Quickstart

Hosted endpoint (recommended)

Zero setup: the endpoint is always on at https://cloud.yepcode.io/mcp.

Prerequisites: YepCode account and an API Credential with MCP endpoints.

OAuth vs No-OAuth

Endpoint	When to use
No-OAuth	Simplest: token in URL or headers. Best for Cursor, Claude Desktop, prototypes.
OAuth	OAuth 2.0 Client Credentials. For enterprise and central credential management.

Both come from the same API Credential. Revoke the credential to invalidate both.

Configure (No-OAuth)

URL with token:

{
  "mcpServers": {
    "yepcode-mcp-server": {
      "url": "https://cloud.yepcode.io/mcp/<your_token>"
    }
  }
}

Or with headers:

{
  "mcpServers": {
    "yepcode-mcp-server": {
      "url": "https://cloud.yepcode.io/mcp",
      "headers": { "Authorization": "Bearer <your_token>" }
    }
  }
}

Replace <your_token> with the value from Settings → API Credentials.

Verification

Tools list appears in your MCP client
run_code executes (if enabled)
Process tools appear (tag with mcp-tool for instant exposure, or add custom tags to YEPCODE_MCP_TOOLS)

Self-host (NPX or Docker)

For air-gapped environments or full control.

Requirements: Node.js >= 18, API token from Settings → API Credentials.

NPX

{
  "mcpServers": {
    "yepcode-mcp-server": {
      "command": "npx",
      "args": ["-y", "@yepcode/mcp-server"],
      "env": { "YEPCODE_API_TOKEN": "your_api_token_here" }
    }
  }
}

Docker

docker build -t yepcode/mcp-server .

{
  "mcpServers": {
    "yepcode-mcp-server": {
      "command": "docker",
      "args": ["run", "-i", "--rm", "-e", "YEPCODE_API_TOKEN=your_token", "yepcode/mcp-server"]
    }
  }
}