An attached server can show In use while a particular assistant still cannot reach its tools. Server approval and the connection’s permission to use that server are separate controls.

Confirm the server is ready

Open PD Modules → MCP Hub → Attached servers. Check the intended server’s state, tool count, Why and Connections columns. If it is waiting for review, changed or not responding, resolve that condition before treating a connection grant as the fix.

Use Tools & risk to confirm that the stored offered tools have been reviewed and assigned appropriate classes. Do not lower a class solely because the assistant’s ceiling is too low.

Grant the intended connection

1. Open Connections and choose Edit on the assistant that should use this server.
2. Find Which attached servers it may reach.
3. Tick the intended server and retain only the other server grants that assistant actually needs.
4. Check the connection’s Ceiling against the tools’ assigned risk and review its read-only override.
5. Review the staff account and other restrictions, then choose Save changes.

Editing retains the connection token; issuing New token is not needed to add or remove a grant. Return to the connection editor to confirm the selected server was saved.

Keep the permitted combination deliberate

By default, a connection that reaches attached servers is not also allowed destructive tools of its own. Third-party tool descriptions enter the assistant’s context alongside your own tools. Do not enable the separate acknowledgement permitting both simply to clear an unexplained refusal.

Prefer a connection whose purpose and limits match the actual task. A provider credential’s permissions remain relevant even after the hub accepts the grant.

Verify with the assistant

Reconnect or refresh the client so it obtains the current tool list. Identify attached tools by the server’s short-name prefix, then inspect Audit trail for the result of an authorised operation.

The Connections count on the server list indicates saved grants. It does not prove that every listed connection is active, unexpired, permitted from its source address or able to pass all other checks. Read the actual refusal before changing unrelated limits.

See the PD MCP Hub Blesta guide for related tasks, or explore PD MCP Hub.