Command+K / docs

What is the public MCP endpoint reference?

Every deployment is reachable at https://mcp.commandplusk.com/<slug> (or your custom domain). It speaks MCP Streamable HTTP: POST JSON-RPC 2.0 envelopes to / with Accept: application/json, text/event-stream. The well-known discovery documents live at /.well-known/oauth-authorization-server and /.well-known/oauth-protected-resource. Anonymous / JWT / OAuth modes are selected per deployment.

URL scheme

  • https://mcp.commandplusk.com/<slug> — default hostname.
  • https://<your-custom-domain> — when configured.
  • /.well-known/oauth-authorization-server, /.well-known/oauth-protected-resource — discovery.

Required headers

http
POST /  HTTP/1.1
Host: mcp.commandplusk.com
Content-Type: application/json
Accept: application/json, text/event-stream
Authorization: Bearer <token>   # JWT or OAuth mode only

The Accept header is mandatory

Per MCP Streamable HTTP, servers reject POSTs without application/json, text/event-stream in Accept with HTTP 406.

Example tools/list call

json
{ "jsonrpc": "2.0", "id": 1, "method": "tools/list" }

Next steps

Pricing & plans
Security & data handling

FAQ

Do you support stdio transport?
No — CMD+K deployments are hosted, so only Streamable HTTP. Clients that need stdio can use mcp-remote as a local proxy.
What HTTP methods are accepted?
POST for JSON-RPC. GET on the same URL returns the server info JSON. OPTIONS for CORS preflight.
Are SSE responses supported?
Yes — when the client sends Accept: text/event-stream the server streams partial tool results. Required by the MCP spec.
← Previous
MCP analytics
Next →
Widget overview