Getting Started¶
Vike supports two authentication methods for MCP clients:
- OAuth 2.1 with Dynamic Client Registration (RFC 7591) — used by Claude Desktop. No API key, no JSON file, no Node.js. One-click connect from inside Claude Desktop.
X-API-KEYheader — used by every other client (Claude Code, Cursor, Gemini CLI, GitHub Copilot, raw HTTP).
Pick the path that matches your client below.
Claude Desktop (recommended — no API key needed)¶
- Open Settings → Connectors → Add custom connector
- Name:
Vike - URL:
https://vike.io/mcp - Leave the OAuth Client ID / Secret fields empty — Vike registers your Claude Desktop automatically (RFC 7591)
- Click Add. A browser tab opens → log into Vike → click Allow
- The 8 Vike tools appear under the hammer icon in the chat input
Revoke access anytime from Account → API Keys → Connected Apps.
Get an API key (for all other clients)¶
- Create an account at vike.io
- Go to Account → API Keys
- Enter a label (e.g.
Cursor) and click Create Key - Copy the key (starts with
vk_) — it won't be shown again
Up to 5 active keys per account. All keys share the same rate limit (100 calls/hour).
Connect your MCP client¶
One command, user-scoped. Restart any open Claude Code session afterwards.
Settings → MCP → Add new server, or edit ~/.cursor/mcp.json:
Create .vscode/mcp.json in your workspace and reload:
Verify the connection¶
Ask your AI assistant:
"Search for PEPE token using Vike"
If the connection is working, the assistant will call the token_search tool and return matching tokens.
Rate limits¶
- 100 calls per hour, shared across all your API keys and OAuth-connected apps
- Each tool has a credit cost (0–3 credits per call)
- Recent calls are visible in Account → MCP Calls
Managing keys and connected apps¶
In Account → API Keys you can:
- Create, rename, or delete API keys (max 5 active)
- See the last-used timestamp for each key
- Revoke any OAuth-connected app (Claude Desktop, etc.) under Connected Apps — revocation takes effect immediately