Connect Speka via MCP

Speka exposes an MCP endpoint for connecting AI assistants and external tools to your workspace.

Endpoint

• POST /mcp — JSON-RPC requests (initialize, tools/list, tools/call)
• GET /mcp — health check

Base URL: https://<docs-domain>/mcp — replace <docs-domain> with your Speka domain.

Authentication

• Header: Authorization: Bearer <API key>
• Create an API key in your Speka profile (Profile → API keys).

All MCP requests require a valid API key. Keep the key secret and pass it only via the Authorization header.

Tools

Available tools via tools/list:

• speka_list_projects — list projects accessible to the API key owner
• speka_list_docs — list documents in a project
• speka_search_docs — search across documents

Detailed input/output schemas are returned by the tools/list method.

Examples

initialize

curl -X POST https://<docs-domain>/mcp \
  -H "Authorization: Bearer $SPEKA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'

tools/list

curl -X POST https://<docs-domain>/mcp \
  -H "Authorization: Bearer $SPEKA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":2,"method":"tools/list","params":{}}'

tools/call

curl -X POST https://<docs-domain>/mcp \
  -H "Authorization: Bearer $SPEKA_API_KEY" \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":3,"method":"tools/call","params":{"name":"speka_list_projects","arguments":{}}}'

Public access

Docs are publicly accessible without authentication; private platform paths (/api, /socket.io/) remain protected.