Skip to main content
After publishing your MCP server, you can connect it to any supported MCP client using the configuration generated by 0mcp. The Setup page provides everything you need, including your MCP endpoint, client-specific configuration, and any required authentication details.
Setup configuration is generated from the currently published version. Publish a version before connecting an MCP client.

​
Supported clients

0mcp provides setup guides for:
  • Claude Code
  • Claude Desktop
  • Cursor
  • Codex
  • VS Code
  • Windsurf
Each guide includes the configuration required for that client. Choose your client from the Setup group in the left sidebar.
Windsurf supports 0mcp when your installed version includes support for remote Streamable HTTP MCP servers.

​
Before you connect

Before configuring a client, make sure you have:
  • Published your MCP server
  • Reviewed any required authentication credentials
  • Stored secrets in environment variables or your client’s secure credential store
  • Resolved any configuration issue shown on the Setup page
Avoid placing API keys or access tokens directly in shared configuration files.

​
Connect your client

  1. Open your server in the 0mcp dashboard.
  2. Navigate to Setup.
  3. Select your MCP client.
  4. Copy the generated configuration.
  5. Add any required environment variables or credentials.
  6. Restart or reconnect your client.
Once connected, your client will discover the published tools, resources, and prompts available on your MCP server.

​
OAuth-protected servers

If your published tools require MCP OAuth metadata, Setup shows the OAuth resource URL and any missing configuration. Configure the OAuth issuer and JWKS URL from server Settings before copying client configuration. If Setup reports that configuration is unavailable, fix the listed OAuth issue and reload the page.

​
Protocol compatibility

0mcp serves hosted MCP endpoints over Streamable HTTP. Modern MCP clients may negotiate the MCP 2026-07-28 protocol era automatically. Older clients may use legacy behavior. See MCP 2026-07-28 compatibility for details about version negotiation, browser headers, and rollout behavior.

​
Troubleshooting

If your client can’t connect to the server, see MCP Connection Issues. If the connection succeeds but no capabilities appear, see Tool Discovery Problems.