Octopus MCP

Once connected, your agent can:

• See your work — list your projects and workspaces, and read the full structure of a sitemap (pages, blocks, colors, tags, symbols).
• Build and edit sitemaps — create and update pages, add content blocks with wireframes, restructure the page tree, apply several changes at once as a single atomic update.
• Manage projects — create, duplicate, archive, move, or delete projects; transfer ownership; update project settings like theme and layout.

Every action runs as you — the agent only ever sees and changes what your Octopus.do account has access to.

Connecting

Endpoint

https://mcp.octopus.do/mcp

The general flow is the same in every client:

1. Add Octopus as a remote MCP server / connector using the endpoint above.
2. Choose OAuth as the authorization type — most clients detect this automatically.
3. Sign in (or register) with your Octopus.do account when the browser opens.
4. Ask your agent to do something — e.g. “show my Octopus projects” or “add a pricing page to my sitemap.”

No API keys to copy or manage — authorization happens through your normal Octopus.do login. Client-specific instructions below.

Claude (web and desktop)

1. Go to Settings → Connectors → Add custom connector.
2. Enter https://mcp.octopus.do/mcp as the URL and click Add.
3. Click Connect and sign in with your Octopus.do account.

Claude Code

Run in your terminal:

claude mcp add --transport http octopus https://mcp.octopus.do/mcp

Then run /mcp inside Claude Code to complete the sign-in.

Cursor

Add to ~/.cursor/mcp.json (or .cursor/mcp.json in your project):

{
  "mcpServers": {
    "octopus": {
      "url": "https://mcp.octopus.do/mcp"
    }
  }
}

Cursor will prompt you to authenticate the first time the server is used.

VS Code (GitHub Copilot)

Run MCP: Add Server from the Command Palette and choose HTTP, or add to .vscode/mcp.json:

{
  "servers": {
    "octopus": {
      "type": "http",
      "url": "https://mcp.octopus.do/mcp"
    }
  }
}

ChatGPT

Requires a plan with connector support and developer mode enabled (Settings → Apps & Connectors → Advanced settings).

1. Go to Settings → Apps & Connectors → Create (or Add connector).
2. Set the MCP server URL to https://mcp.octopus.do/mcp and authentication to OAuth.
3. Complete the Octopus.do sign-in when prompted.

Windsurf

Add to ~/.codeium/windsurf/mcp_config.json:

{
  "mcpServers": {
    "octopus": {
      "serverUrl": "https://mcp.octopus.do/mcp"
    }
  }
}

Other MCP clients

Any client that supports remote MCP servers (Streamable HTTP) with OAuth works: point it at https://mcp.octopus.do/mcp, pick OAuth, and sign in with your Octopus.do account.

Authentication

Octopus MCP uses OAuth 2.1, the standard MCP clients use for secure, per-user authorization. Your agent requests access on your behalf, you approve it once during sign-in, and access can be revoked from your Octopus.do account at any time. The MCP server itself never sees or stores your password.

Available tools

Your agent picks these tools on its own — you don’t call them directly. The reference below is useful when you want to know exactly what the agent can (and can’t) do, or to phrase a request precisely.

Most write tools accept an optional idempotency_key (string): a unique key that makes retries safe — a repeated request with the same key is applied only once. It’s omitted from the tables below (delete_project is the one write tool that doesn’t take it).

Destructive actions (like deleting a page or a project) are flagged to your AI client, which will typically confirm with you before running them.

Reading

get_me

Returns your account name. No parameters.

list_projects

Lists all projects you can access, across every workspace (personal and teams). Each item includes the workspace it belongs to. No parameters.

list_workspaces

Lists your workspaces (personal + teams) with folders and the projects inside each. No parameters.

get_workspace

Returns one workspace: info, folders, and projects.

get_project

Returns the full state of one project: the entities (tabs, sections, nodes = pages, blocks, colors, tags, symbols, arrows, …), the parent/child tree linking them.

Editing

apply_changes

Applies several editing operations to a project as one atomic change — the preferred way to build or restructure a sitemap. Operations run in order and each sees the effect of the previous ones. Give a created entity a ref and reference it in later operations via parent_ref / node_ref instead of an id.

Each operation:

Operation names follow group.action:

create_node

Creates a page (node) in the sitemap.

update_node

Updates page fields.

move_node

Moves a page with its whole subtree to another parent.

delete_node

Deletes a page with its whole subtree and all blocks inside.

create_block

Creates a content block inside a page.

update_block

Updates block fields.

move_block

Moves a block to another page.

delete_block

Deletes a block from its page.

Project management

create_project

Creates a new project in the target workspace. May fail when your plan’s project limit is reached.

delete_project

Permanently deletes a project with all its content. This cannot be undone.

manage_project

Project lifecycle actions: duplicate, archive/unarchive, move, transfer.

update_project_settings

Updates project-level settings.

Learn more

• Octopus.do: https://octopus.do/
• Model Context Protocol: https://modelcontextprotocol.io/