Shared settings for Spoki MCP: the server URL, how to sign in, how to create an API key, and setup for other clients (mcp-remote, custom code).
Looking for Claude, ChatGPT, Cursor, VS Code, or n8n? Start from Get Started with Spoki MCP.
Server URL #
Use this address in every client. Copy it exactly: no extra spaces or trailing characters:
https://mcp.spoki.com/v2/mcp
Do not use staging hosts or older /mcp paths.
Two ways to connect #
| Mode | When to use | How |
|---|---|---|
| Spoki login | Claude, ChatGPT, and clients with a sign-in button | Sign in to Spoki, pick the account, click Allow. Do not paste an API key. |
| API key | Cursor, n8n, VS Code fallback, custom code, local bridges | Send header X-Spoki-Api-Key with your key. |
Get your API key #
- In Spoki, go to app.spoki.it → Integrations → Spoki MCP → Request Api Key.
- Copy the key.
- Keep it private. Anyone with the key can use your Spoki account.
You’re done when… #
- You have a Spoki API key copied somewhere safe (or you only use Spoki login and do not need a key).
- You know which mode your client uses (login vs API key).
Generic MCP client settings #
| Setting | Value |
|---|---|
| Transport | Streamable HTTP |
| URL | https://mcp.spoki.com/v2/mcp |
| Header name | X-Spoki-Api-Key |
| Header value | Your API key |
n8n #
For the full n8n checklist (AI Agent → MCP Client Tool → Header Auth), see Spoki MCP with n8n.
Clients that need mcp-remote #
Some clients only start local MCP servers. Use mcp-remote as a bridge (Node.js required). Always include --transport and http-only, or the bridge ignores your API key and opens a login page.
{
"mcpServers": {
"spoki": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://mcp.spoki.com/v2/mcp",
"--transport",
"http-only",
"--header",
"X-Spoki-Api-Key: YOUR_API_KEY"
]
}
}
}
For Claude Desktop local servers, paste this into claude_desktop_config.json (Settings → Developer → Edit Config), replace YOUR_API_KEY, save, and restart Claude Desktop. Local setup works only while your computer is on. For Claude on the web, mobile, or scheduled tasks, use the Claude guide instead.
Test your API key #
Replace YOUR_API_KEY with your key:
curl -X POST https://mcp.spoki.com/v2/mcp \
-H "X-Spoki-Api-Key: YOUR_API_KEY" \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"test","version":"1.0"}}}'
A valid key returns a response with "serverInfo". An invalid key returns invalid_api_key.
Common problems #
- invalid_api_key: Create a new key in Spoki Integrations → Spoki MCP, and paste it without spaces.
- Login page instead of tools: For mcp-remote, add
--transport http-only. For Claude/ChatGPT, use Spoki login, not an API key. - Wrong or old URL: Use only
https://mcp.spoki.com/v2/mcp.
Need help? support@spoki.com.
