MCP and Cursor

You will learn how Dokko exposes MCP, how to create a personal API key, and how to wire Cursor safely.

Dokko implements the Model Context Protocol so agents can list spaces, search pages, read content, and (with permission) apply safe updates using the same rules as the REST API.

Choose a transport

Transport	Best for
Streamable HTTP at `https://api.dokko.cloud/v1/mcp/http`	Cursor and other remote MCP hosts (recommended)
SSE at `/v1/mcp/sse`	Older MCP clients that expect classic SSE
stdio (`dokko-mcp` binary)	Local development with direct Postgres access

Most users should use Streamable HTTP with a personal API key — no local database required.

Create a personal API key

Sign in to Dokko and open Settings → API keys.
Click Create key, name it for the client (for example cursor-work-laptop).
Copy the key immediately. Dokko shows the secret once (dok_<prefix>_<secret>).

Store the key in your OS secret store or Cursor plugin configuration — not in git, screenshots, or shared docs. Revoke keys you no longer use from the same settings screen.

API keys authenticate as you. They inherit your workspace permissions. They are for agents and automation, not for handing to untrusted third parties.

Cursor plugin (recommended)

The Dokko repository ships a Cursor plugin that points at hosted Streamable HTTP and prompts for DOKKO_API_KEY under Customize → Plugins → Dokko → Configure.

High-level steps:

Copy the plugin files into a real folder under ~/.cursor/plugins/local/dokko (Cursor ignores symlinks outside that tree).
Reload the Cursor window.
Configure the plugin with a key from Settings → API keys.
Remove duplicate dokko entries from ~/.cursor/mcp.json so the server is not loaded twice.

The plugin uses ${DOKKO_API_KEY} substitution from Cursor’s plugin settings — not ${env:DOKKO_API_KEY} unless you intentionally manage the variable in your shell environment.

Manual `mcp.json` (alternative)

You can add a remote server entry yourself. Every request must send the key:

{
  "mcpServers": {
    "dokko": {
      "url": "https://api.dokko.cloud/v1/mcp/http",
      "headers": {
        "X-API-Key": "dok_your_prefix_your_secret"
      }
    }
  }
}

Prefer the plugin prompt over committing a key into a project file.

What MCP can do

Tools mirror product capabilities: discovery (dokko_context, search_pages, get_page), comments, and guarded page updates. Destructive or high-volume operations may be rate-limited. Spaces excluded from AI or workspaces with AI disabled block retrieval the same way Ask Dokko does.

Read the operator-facing tool list in the Dokko API repository (docs/mcp.md) when you need exact tool names and write policies.