Via stdio

Depending on the version of your client application, remote MCP's may need to use mcp-remote to proxy Streamable HTTP into stdio.

Direct Connection (Recommended)

If your client supports it, it's recommended to connect to the Streamable HTTP endpoint directly such as:

{
  "mcpServers": {
    "remote-mcp": {
      "type": "sse",
      "url": "https://mcp-server-with-next-js.vercel.app/api/mcp"
    }
  }
}

Using mcp-remote (Alternative)

Due to client versions, and varying levels of support, you can list mcp-remote as the method for end users to connect to your MCP server.

The above set up snippet will then look like:

"remote-example": {
  "command": "npx",
  "args": [
    "mcp-remote",
    "-y",
    "http://localhost:3000/api/mcp" // this is your app/api/[transport]/route.ts
  ]
}