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 server doesn’t show up in my client

After editing your client’s MCP config, you usually need to fully restart the client (not just close the chat window). Check the client’s “MCP servers” or “Tools” panel — if Peaka doesn’t appear, the config wasn’t picked up. If it appears but reports an error on startup, look at the client’s MCP logs:
  • Claude Desktop: ~/Library/Logs/Claude/mcp*.log (macOS) or %APPDATA%\Claude\logs\mcp*.log (Windows)
  • Cursor / Windsurf / VS Code: the Output panel — choose the MCP/extension channel
  • Claude Code: claude mcp list and inspect the named server

​
OAuth window never opens (remote)

The remote server returns 401 Unauthorized with OAuth metadata on the first request, and the client is expected to open a browser. If that doesn’t happen:
  • Confirm your client supports remote MCP with OAuth.
  • Some clients cache failed auth attempts. Remove the server from the client config, restart, and re-add it.

​
”401 Unauthorized” on every call

  • Remote: your token expired or was revoked. Re-trigger OAuth by removing and re-adding the server in your client.
  • NPM / from source: PEAKA_API_KEY is missing, malformed, or revoked. Re-issue the key in Peaka and update the env block in your client config.

​
peaka_list_projects returns only one project

Expected when authenticating with a Project API key — the key is bound to a single project. To enumerate projects across organizations and workspaces, use a Partner API key or the remote server with OAuth.

​
The assistant keeps asking for projectId

Every project-scoped tool call needs a projectId. The remote server is stateless about which project you’re working with — the assistant is instructed to ask once per session and reuse the answer. If it asks more often than that, mention the project up front: “In my analytics-prod project, list the tables in the events schema.”

​
Cache or metadata refresh seems stuck

Both are async. Check status with:

​
Environment variables

The local installs read one variable:
NameDescription
PEAKA_API_KEYProject or Partner API key. Required for NPM and from source installs. The remote server uses OAuth and does not read this variable.

​
Still stuck?