Octopad
Give Claude or Cursor a shared back-office over MCP so multiple agents see the same tasks, knowledge base, and session context.
Overview
Octopad is an MCP server for the Build phase that exposes a shared back-office workspace—tasks, knowledge, and context—for your team’s AI agents over streamable HTTP.
What is this MCP server?
- Streamable HTTP MCP endpoint at mcp.octopad.app for Claude Code, Cursor, and other MCP clients
- Shared tasks, knowledge, and context so team or multi-agent setups stay aligned
- Back-office metaphor: operational layer for AIs rather than a single-purpose API bridge
- Hosted remote server (version 0.1.0)—no local stdio install in server.json
- Works as context hub during build and operate when you iterate on agent playbooks
- Protocol: Model Context Protocol remote (streamable-http)
- Published server version: 0.1.0
- Single documented remote URL: https://mcp.octopad.app/mcp
What problem does it solve?
Agent chats fragment tasks and context across sessions, so solo builders waste time re-explaining decisions and lose track of what each AI was supposed to do.
Who is it for?
Indie teams or power users running multiple MCP agents who want a lightweight shared task and knowledge layer without building custom ops tooling.
Skip if: Builders who only need a single chat with one agent and no persistent team knowledge store.
What do I get? / Deliverables
After you register the Octopad MCP remote, your agents can read and update shared tasks and knowledge from one workspace instead of isolated threads.
- MCP-connected shared workspace for agent tasks and knowledge
- Persistent context agents can load on each session
- Central back-office instead of per-chat state
Recommended MCP Servers
Journey fit
Octopad sits in Build because solo builders wire it into their agent stack once the product direction is set and they need durable coordination—not ad-hoc chat threads. Agent-tooling is the canonical shelf: it is an MCP remote workspace for AI workflows, not a one-off integration or a ship-time checker.
How it compares
MCP workspace for agent coordination, not a generic developer-tools skill or a raw GitHub integration.
Common Questions / FAQ
Who is Octopad for?
Solo builders and small teams using Claude Code, Cursor, or other MCP clients who want shared tasks, knowledge, and context for several AIs.
When should I use Octopad?
Use it during Build and Operate when you outgrow one-off chats and need a stable back-office layer wired into your agent via MCP.
How do I add Octopad to my agent?
Add the streamable HTTP remote https://mcp.octopad.app/mcp in your client’s MCP config (Claude Code, Cursor, etc.) per Octopad’s setup docs on octopad.ai.