PD MCP Hub can make a remote MCP server’s tools available through your billing installation. Attaching first fetches the server’s tool list; it does not immediately give those tools to every assistant.

Check the server’s connection method

Use a provider-documented Streamable HTTP MCP endpoint over HTTPS. A normal website URL, a generic REST API address or a local program command is not interchangeable with that endpoint.

This procedure covers a server that needs no credential or accepts a bearer API token. Confirm the provider’s actual method before you begin. A visible authentication option does not prove that every configuration required by that provider is available in the form.

Fetch its tools

1. Open PD Modules → MCP Hub → Attached servers → Attach a server.
2. Choose an offered starting point or Type an address myself.
3. Fill Name it with a recognisable name and Short name with a distinct lower-case name using letters, digits and hyphens.
4. Enter the provider’s HTTPS MCP endpoint in Address.
5. Choose No credential needed, or An API key or token for the supported bearer-token arrangement. Enter only the provider credential required for that server in The credential.
6. Choose Fetch its tools, then inspect the resulting server row and any refusal or error.

The short name prefixes its exposed tools, helping you distinguish attached tools from the hub’s own tools. Use a credential scoped for the intended provider tasks; the hub’s later risk classification is not a substitute for provider-side permissions.

Complete the remaining steps

Open Tools & risk to review the offered tools and assign appropriate risk classes. Approve the reviewed definitions only when you understand what is being made available. Then explicitly select this server on each connection that should reach it and check the connection ceiling.

If authentication needs a custom header name or OAuth token settings that the form does not let you enter, keep the integration unconfigured and ask PD Modules support whether the module supports that provider-documented arrangement. Do not paste extra values into unrelated fields, put secrets in the address or use your hub connection token as a provider credential.

If a fetch reports an uncertain result, check the server list before submitting another attachment with the same purpose.

Check the endpoint and authentication

Your hosting team should confirm the provider-documented HTTPS Streamable HTTP endpoint and supported authentication method. Check billing-server reachability separately from provider authentication, and inspect the saved attachment list after an uncertain fetch. If the provider requires custom-header or OAuth settings absent from the form, keep that integration unconfigured and ask PD Modules support about the supported module arrangement, supplying the provider’s public documentation without credentials.

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