Connect an existing server

Paste your MCP server URL to use Chat, testing, publish checks, and the submission pack without Manufact hosting.

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

Manufact creates an external (URL-connected) server that proxies your endpoint through the gateway. There is no build, deployment, or repository connection.

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 do not need Manufact-hosted deployments, runtime logs, environment variables, analytics, observability, Public Chat, or custom domains

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:

Entry pointRoute
Servers → New ServerScroll to Connect an existing server at the bottom of the new-server page
Onboarding → ConnectFirst sign-in wizard, Connect tile — see Onboarding
Marketing CTAsLog in via /cloud/connect-external (with optional url and feature query params)
Connect an existing server form on the New Server page

Step-by-step

  1. Paste the full MCP endpoint URL, for example https://your-mcp-server.com/mcp. Manufact accepts http:// and https:// URLs.
  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
    • Onboardingpublish checklist with autorun=1
URL field showing a successful connection

OAuth

External servers that use OAuth store tokens on the server record after you authenticate. If your endpoint's auth requirements change, reconnect from Settings → External MCP URL.

What you get vs. hosted servers

FeatureExternal (URL-connected)Manufact-hosted
Overview, Chat, Tools, Prompts, ResourcesYesYes
Testing, Checklist, Submission packYesYes
Public ChatNoYes
Deployments, preview environmentsNoYes
Runtime logsNoYes
Environment variablesNoYes
Analytics, ObservabilityNoYes
Domains (slug / custom)NoYes

Hosted servers route traffic through Manufact's build and deploy pipeline. External servers proxy live requests to your URL through the gateway.

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. Creation is designed for the dashboard flow above. The REST API accepts POST /api/v1/servers with type: "external" and a url field for integrations that need it.

Next steps

On this page