Connect an existing server

Use this path when your MCP server is already hosted elsewhere and you want Manufact's dashboard tools and publish workflow without deploying code on the platform.

Manufact first creates a direct external server: dashboard testing and publishing tools connect to your URL, while your clients keep using that URL unchanged. You can later enable the Manufact proxy to add a stable gateway URL, analytics, domains, and other gateway products. There is no Manufact build, deployment, or repository connection in either mode.

When to use this

• You run MCP on your own infrastructure, another cloud, or a third-party host
• You want Chat, the inspector (Tools, Prompts, Resources), Testing, the publish checklist, and the submission pack
• You want to test first and decide later whether client traffic should use the Manufact gateway

For full hosting with auto-deploy on push, see the Quickstart or Creating servers.

Where to start

You can connect by URL from three places:

Step-by-step

1. Paste the full HTTPS MCP endpoint URL, for example https://your-mcp-server.com/mcp.
2. After you stop typing, Manufact probes the endpoint (about 750 ms debounce) to discover capabilities and read the server name.
3. If the server requires OAuth, click Authenticate, complete the flow, then continue.
4. When the status shows Connected, click Connect.
5. Manufact creates the server and opens:
   • New Server page → server Overview
   • Onboarding → publish checklist with autorun=1

Direct vs. proxied external servers

Direct external servers use your upstream URL for dashboard connections. Proxied external servers retain that URL as the upstream target while exposing a separate Manufact gateway URL to clients.

Enable the Manufact proxy

Open a direct external server's Settings and select Upgrade to Manufact proxy. Activation keeps your upstream URL and authentication, creates a Manufact URL, and unlocks gateway products. Gateway traffic uses your organization's existing credits and normal metering.

To revert, select Downgrade to external URL on the same Settings card. The Manufact URL stops working immediately; clients must connect to your external MCP URL directly, and gateway analytics, sessions, domains, Public Chat, and traffic controls are disabled.

Update the URL later

Open the server's Settings tab. External servers show External MCP URL instead of Repository. Paste a new URL, re-authenticate if needed, and click Save. See Server settings.

Programmatic creation

There is no CLI or Manufact MCP tool to create external servers today. The REST API preserves direct creation and provides separate proxy operations:

• POST /api/v1/servers with type: "external" creates a direct server, matching the dashboard flow.
• POST /api/v1/servers/{id}/proxy idempotently enables the proxy for an existing direct external server.
• DELETE /api/v1/servers/{id}/proxy idempotently disables the proxy and returns the server to its external URL.

Create a direct connection:

{
  "type": "external",
  "organizationId": "<uuid>",
  "url": "https://customer.example/mcp",
  "name": "Customer MCP",
  "auth": { "type": "bearer", "token": "<token>" }
}

To upgrade an existing direct connection, send an authenticated POST request with no body to /api/v1/servers/{id}/proxy. The operation returns the enriched server; its canonical mcpUrl is the Manufact gateway URL after proxy activation.

To downgrade a proxied external server, send an authenticated DELETE request to /api/v1/servers/{id}/proxy. The Manufact gateway URL stops working immediately and the server's canonical mcpUrl reverts to the external upstream URL.

Next steps