Skip to main content
The Prompting Company hosts a remote MCP server at: 
https://app.promptingco.com/api/mcp
This server uses Streamable HTTP and OAuth 2.1. In clients that support remote MCP natively, you usually only need the server URL. The client will handle dynamic client registration and open the browser for authentication automatically.
You do not need to manually create or paste an OAuth client ID or client secret in normal MCP client setup. Native remote MCP clients register themselves during the OAuth flow.

​
Server Details

  • MCP transport URL: https://app.promptingco.com/api/mcp
  • Protected resource metadata: https://app.promptingco.com/.well-known/oauth-protected-resource/api/mcp
  • Authorization server metadata: https://app.promptingco.com/.well-known/oauth-authorization-server/api/auth

​
Before You Start

Make sure the client you are using can reach https://app.promptingco.com over the public internet. During authentication:
  1. Your MCP client opens the browser.
  2. You sign in to The Prompting Company if needed.
  3. You approve the consent screen.
  4. The browser returns control back to the MCP client.

​
Claude

​
Claude.ai / Claude Desktop

  1. Open Settings -> Connectors.
  2. Add a custom MCP server.
  3. Enter this server URL:
https://app.promptingco.com/api/mcp
  1. Start the connection flow.
  2. Complete sign-in and approval in the browser.
  3. Return to Claude once the browser finishes redirecting.
Claude connects from Anthropic-managed infrastructure. If you are testing a non-production environment, the MCP endpoint must be publicly reachable and the OAuth metadata must advertise the same public hostname the client is using.

​
Claude Code

Run: 
claude mcp add --transport http tpc https://app.promptingco.com/api/mcp
Then, inside Claude Code, run: 
/mcp
Claude Code will start the OAuth flow in your browser.

​
Codex

Run: 
codex mcp add tpc --url https://app.promptingco.com/api/mcp
If this is your first remote MCP server in Codex, enable the RMCP client in ~/.codex/config.toml: 
[features]
experimental_use_rmcp_client = true
Then log in: 
codex mcp login tpc
You can also configure it directly in ~/.codex/config.toml: 
[features]
experimental_use_rmcp_client = true

[mcp_servers.tpc]
url = "https://app.promptingco.com/api/mcp"

​
Cursor

If Cursor supports remote MCP URLs directly in your version, use: 
https://app.promptingco.com/api/mcp
If you need a stdio bridge instead, configure: 
{
  "mcpServers": {
    "tpc": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://app.promptingco.com/api/mcp"]
    }
  }
}

​
Visual Studio Code

Use the stdio bridge with mcp-remote: 
{
  "mcpServers": {
    "tpc": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://app.promptingco.com/api/mcp"]
    }
  }
}
You can also add it through the Command Palette:
  1. Run MCP: Add Server
  2. Choose Command (stdio)
  3. Enter:
npx -y mcp-remote https://app.promptingco.com/api/mcp
  1. Name it tpc
  2. Start the server from MCP: List Servers

​
Windsurf

Add this to your MCP server configuration: 
{
  "mcpServers": {
    "tpc": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://app.promptingco.com/api/mcp"]
    }
  }
}

​
Zed

Add this to your settings: 
{
  "context_servers": {
    "tpc": {
      "source": "custom",
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://app.promptingco.com/api/mcp"],
      "env": {}
    }
  }
}

​
Other Clients

For clients that do not support remote MCP with OAuth natively, use:
  • Command: npx
  • Arguments: -y mcp-remote https://app.promptingco.com/api/mcp

​
Troubleshooting

​
Browser auth succeeds but the client does not connect

  • Close the MCP client and reopen it.
  • Remove the existing MCP connection and add it again.
  • Make sure the server URL is exactly https://app.promptingco.com/api/mcp.
  • Complete the approval in a normal browser window instead of an embedded browser if your client gives you the option.
  • Retry with a fresh connection attempt so you get a fresh signed OAuth URL.
  • If you are testing through a proxy or tunnel, make sure OAuth metadata and the MCP transport both use the same public hostname.

​
Client cannot discover the server

Verify these URLs load successfully: 
https://app.promptingco.com/api/mcp
https://app.promptingco.com/.well-known/oauth-protected-resource/api/mcp
https://app.promptingco.com/.well-known/oauth-authorization-server/api/auth
Expected behavior:
  • /api/mcp returns 401 when you are not authenticated yet
  • both well-known endpoints return 200