Skip to Content
GatewaysMCP Gateway

MCP Gateway

Expose your tools to any MCP-compatible client. An MCP gateway serves your tools over JSON-RPC 2.0 so Claude Code, Cursor, Windsurf, and VS Code Copilot can list and call them directly. almyty supports HTTP, SSE, and WebSocket transports.

MCP endpoints on the gateway Integrations tab

Create the gateway

  1. Open Gateways in the sidebar and click Create Gateway
  2. Select MCP as the protocol

Create Gateway dialog

  1. Enter a name, a slug (used in the endpoint URL), and an optional description
  2. Under Transport, choose HTTP (default), SSE, or WebSocket
  3. Click Create

On the gateway detail page, open the Tools tab to assign the tools this gateway should expose, then use the Authentication tab to add an auth method before going live.

Assigning tools on the gateway Tools tab

Your MCP endpoint follows this pattern:

https://api.almyty.com/{org}/{gateway-slug}

Connect a client

Claude Code

claude mcp add petstore --transport http https://api.almyty.com/acme/petstore

Pass your gateway key as an x-api-key header (generate it in the gateway’s Authentication panel).

Claude Desktop

Add to claude_desktop_config.json:

{ "mcpServers": { "petstore": { "url": "https://api.almyty.com/acme/petstore", "headers": { "x-api-key": "your-gateway-key" } } } }

Cursor / Windsurf

Add to .cursor/mcp.json:

{ "mcpServers": { "petstore": { "url": "https://api.almyty.com/acme/petstore", "headers": { "x-api-key": "your-gateway-key" } } } }

Claude client configured with an almyty gateway

Once connected, the client calls tools/list and tools/call for you. You do not build those requests by hand.

Transport options

TransportURL patternUse case
HTTPPOST /{org}/{slug}Standard request-response
SSEGET /{org}/{slug}/sseStreaming, long-running tools
WebSocketWS /{org}/{slug}/wsBidirectional, real-time

MCP tool schema

Tools exposed through the gateway follow the MCP tool format:

{ "name": "get_users", "description": "Retrieve a list of users with pagination", "inputSchema": { "type": "object", "properties": { "page": { "type": "integer", "description": "Page number" }, "limit": { "type": "integer", "description": "Items per page" } }, "required": [] } }

OAuth 2.1

MCP gateways with OAuth enabled expose discovery endpoints automatically:

https://api.almyty.com/acme/petstore/.well-known/oauth-authorization-server https://api.almyty.com/acme/petstore/.well-known/oauth-protected-resource

On 401 responses, the gateway returns a WWW-Authenticate header linking to the protected resource metadata so MCP clients can start the OAuth flow automatically. See Gateway Authentication for the full OAuth 2.1 walkthrough.

Error codes

MCP errors follow JSON-RPC 2.0:

CodeMeaning
-32700Parse error
-32600Invalid request
-32601Method not found
-32602Invalid params
-32603Internal error