Inkbloc
Connect your agent to Inkbloc so specs, playbooks, and collaborative docs gain interactive AI blocks you can update from Claude Code or Cursor.
Overview
Inkbloc MCP is a MCP server for the Build phase that connects agents to Inkbloc collaborative documents with interactive AI blocks.
What is this MCP server?
- inkbloc-mcp npm package v0.1.2 with stdio transport
- Requires INKBLOC_API_KEY from inkbloc.ai Settings (secret, required)
- Collaborative document workspace with interactive AI blocks agents can read and drive
- Fits specs, decision logs, and living handoff docs beside your codebase
- Cloud SaaS connector—local repo files stay separate unless you sync content into Inkbloc
- Server version 0.1.2
- npm identifier: inkbloc-mcp
- Required env: INKBLOC_API_KEY
What problem does it solve?
Builders duplicate context between their agent chat and a separate doc tool, breaking flow when specs and AI-assisted blocks live only in a SaaS workspace.
Who is it for?
Solo founders already on Inkbloc who want Claude Code or Cursor to read and update living docs and embedded AI blocks.
Skip if: Teams that want only local Markdown in-repo with no Inkbloc account or API key.
What do I get? / Deliverables
With INKBLOC_API_KEY configured, your agent can work Inkbloc documents and AI blocks directly from the MCP host.
- Live MCP connection to Inkbloc documents from your agent
- Agent-driven reads and updates to pages with interactive AI blocks
- Single workspace for specs and handoff docs alongside coding sessions
Recommended MCP Servers
Journey fit
Most solo builders first adopt Inkbloc while drafting product docs, PRDs, and runbooks during Build, even though the same workspace later supports launch copy and growth content. Docs is the canonical shelf because MCP access centers on structured documents and AI-augmented blocks—not deploying backend services.
How it compares
Hosted collaborative-docs MCP bridge, not a static Markdown linter skill.
Common Questions / FAQ
Who is inkbloc for?
Inkbloc MCP is for builders using the Inkbloc workspace who want their coding agent to interact with collaborative documents and interactive AI blocks through MCP.
When should I use inkbloc?
Use it when product specs, runbooks, or marketing docs live in Inkbloc and you need the agent to fetch or update that content during build, launch, or content workflows.
How do I add inkbloc to my agent?
Create an API key at inkbloc.ai Settings, install inkbloc-mcp (v0.1.2), add a stdio MCP server entry with INKBLOC_API_KEY set as a secret env var, and restart your MCP client.