Removing an attached server withdraws its tools from MCP Hub and removes the saved permission for connections to reach that attachment. It is useful when an integration is being retired or should no longer be available through the hub.

Confirm the integration you are retiring

Open PD Modules → MCP Hub → Attached servers. Match the name, short name and address to the integration you intend to remove. Check Connections so you know which assistants may be affected; that column summarises grants rather than proving that each connection is currently usable.

If you only need one assistant to stop using the service, edit that connection and untick the server under Which attached servers it may reach. Removing the attachment affects every connection that used it.

Remove the attachment

1. On the intended server row, choose Remove.
2. Read and confirm the notice that its tools disappear from every connection.
3. Confirm that the attachment is no longer listed.
4. Refresh the affected assistants’ tool lists and review their planned tasks before continuing.

The reviewed tool definitions and this attachment’s connection grants are removed. A later attachment using the same short name does not restore the old grants; review the new tools and authorise connections again.

Understand what removal does not undo

Removing the hub attachment does not cancel completed provider operations or revoke the credential at the provider. If that provider credential is no longer needed, arrange its retirement through the provider’s normal authorised process. Do not assume the hub’s Remove button performs that external account action.

The assistants’ own hub connections remain separate records. Do not delete them unless those connections themselves should be retired. Check Audit trail and the target service when reconciling an operation that was already in progress or had an uncertain result.

If you need the integration again, treat it as a new attachment: use the documented endpoint, fetch its tools, review risk and definitions, then select it on the intended connections. Keep the provider credential out of support messages and screenshots.

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