Skip to main content

Documentation Index

Fetch the complete documentation index at: https://docs.peaka.com/llms.txt

Use this file to discover all available pages before exploring further.

The Peaka MCP server works with any client that supports the Model Context Protocol. Pick your client below for the right config snippet and a link to its “add an MCP server” instructions. Two configuration patterns appear throughout this page:
  • Remote (recommended). Point the client at https://mcp.peaka.studio/mcp and authenticate via OAuth. Some clients accept a remote URL natively; others use the mcp-remote bridge to expose it as a stdio server.
  • Local (NPM). Run @peaka/mcp-server-peaka via npx and authenticate with PEAKA_API_KEY.
For everything else (auth modes, env vars), see Authentication.

​
Claude Desktop

Add an MCP server in Claude Desktop ↗ Remote — Claude Desktop adds remote MCP servers through the UI, not the JSON config file.
1

Open Settings → Connectors

Click your name in the bottom-left, then Settings → Connectors.
2

Add custom connector

Click Add custom connector and paste https://mcp.peaka.studio/mcp as the MCP Server URL.
3

Authenticate

Claude Desktop opens the OAuth flow in your browser. Sign in to Peaka and approve.
NPM — for the local, API-key path, edit claude_desktop_config.json:
  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json
  • Windows: %APPDATA%\Claude\claude_desktop_config.json
{
  "mcpServers": {
    "peaka": {
      "command": "npx",
      "args": ["-y", "@peaka/mcp-server-peaka@latest"],
      "env": { "PEAKA_API_KEY": "<YOUR_API_KEY>" }
    }
  }
}
Restart Claude Desktop after editing.

​
Claude Code

Add an MCP server in Claude Code ↗ 
# Remote
claude mcp add --transport http peaka https://mcp.peaka.studio/mcp

# NPM
claude mcp add peaka -- npx -y @peaka/mcp-server-peaka@latest -e PEAKA_API_KEY=<YOUR_API_KEY>

​
Cursor

Add an MCP server in Cursor ↗ Edit ~/.cursor/mcp.json (macOS/Linux) or %USERPROFILE%\.cursor\mcp.json (Windows): 
{
  "mcpServers": {
    "peaka": {
      "url": "https://mcp.peaka.studio/mcp"
    }
  }
}

​
Windsurf

Add an MCP server in Windsurf ↗ Edit ~/.codeium/windsurf/mcp_config.json: 
{
  "mcpServers": {
    "peaka": {
      "serverUrl": "https://mcp.peaka.studio/mcp"
    }
  }
}

​
VS Code (GitHub Copilot)

Add an MCP server in VS Code ↗ Edit .vscode/mcp.json in your workspace, or your user-level mcp.json: 
{
  "servers": {
    "peaka": {
      "type": "http",
      "url": "https://mcp.peaka.studio/mcp"
    }
  }
}

​
Zed

Add an MCP server in Zed ↗ Open the command palette → agent: add context server, or edit settings.json: 
{
  "context_servers": {
    "peaka": {
      "command": {
        "path": "npx",
        "args": ["-y", "mcp-remote", "https://mcp.peaka.studio/mcp"]
      }
    }
  }
}

​
Cline

Add an MCP server in Cline ↗ Open Cline → MCP Servers → Configure MCP Servers: 
{
  "mcpServers": {
    "peaka": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://mcp.peaka.studio/mcp"]
    }
  }
}

​
ChatGPT (Custom Connectors)

Add a custom connector in ChatGPT ↗ In ChatGPT settings → Connectors → Add custom connector, enter:
  • MCP Server URL: https://mcp.peaka.studio/mcp
  • Authentication: OAuth
ChatGPT walks you through the OAuth flow.

​
Any other client

Any MCP-compliant client can connect. Use one of the patterns above as a template:
  • If the client supports remote MCP natively, give it https://mcp.peaka.studio/mcp.
  • If it only supports stdio, wrap the URL with npx -y mcp-remote https://mcp.peaka.studio/mcp.
  • If you’d rather use an API key, run npx -y @peaka/mcp-server-peaka@latest with PEAKA_API_KEY in the environment.
See Quickstart for the minimal setup, Tools reference for what the assistant can do once connected, and Troubleshooting if something doesn’t light up.