get_capabilities
Return the server contract, transports, and honest session boundary.
Preparando el lienzo…
Model Context Protocol / v0.1
Docs Studio MCP exposes the real loop behind the app: parse a brief, draft onto a document, inspect blocks, propose reviewable edits, and export the result.
Official TypeScript SDK · persistent DynamoDB workspace · Streamable HTTP
THE EXPOSED SURFACE
The contract is intentionally close to what the web app already does. Drafting applies the first version; later changes are proposals with an explicit accept or reject step.
Return the server contract, transports, and honest session boundary.
Open a blank Letter or Legal workspace, optionally seeded with HTML.
List persistent documents belonging to the authenticated workspace.
Return HTML, plain text, blocks, word count, brief context, and pending edits.
Extract tasks, objectives, constraints, learning outcome, and rubric weights.
Run the same streaming draft endpoint used by the Docs Studio canvas.
Use the document copilot; AI changes return as reviewable proposals.
Create a named proposal without mutating the current document.
Apply a proposal only after the source document still matches.
Close a proposal and leave the document untouched.
Add an editable MathJax equation to the document.
Add an editable HTML table with a header row.
Return recent document events for review and audit.
Return HTML, DOCX, or PDF as content/base64.
READ-ONLY CONTEXT
docs://workspaceList persistent documents for the signed-in owner.
docs://document/{documentId}HTML, text, blocks, brief, and pending review proposals.
docs://history/{documentId}Created, drafted, proposed, accepted, rejected, inserted, exported.
THE IMPORTANT PART
Every mutating path is visible in the API. The review boundary is part of the protocol, not a promise in the UI copy.
CONNECT IN A MINUTE
Sign into Docs Studio with Google and create a personal MCP credential. Any client that supports Streamable HTTP can use it; the credential sees only that user's persistent workspace.
{
"mcpServers": {
"docs-studio": {
"command": "npx",
"args": ["tsx", "src/mcp/server.ts"],
"cwd": "/path/to/docs-studio",
"env": {
"DOCS_STUDIO_URL": "http://localhost:9003"
}
}
}
}Or run npm run mcp:stdio from the repository.
{
"mcpServers": {
"docs-studio": {
"url": "https://docss.studio/api/mcp",
"headers": {
"Authorization": "Bearer dsm_YOUR_PERSONAL_TOKEN"
}
}
}
}The token is created once from the signed-in workspace, stored hashed, and can be revoked. It starts with all currently available MCP permissions.
WHAT IS TRUE TODAY
This is a working integration, not a fictional “agent platform”. Here is where the implementation is complete and where the next product work belongs.
Create → draft → read → propose → accept/reject → export.
Streamable HTTP at https://docss.studio/api/mcp with a personal Bearer credential.
Consequential edits can remain proposals until an agent or user explicitly accepts them.
An agent works on persistent documents, not silently on the cursor or selection in an open browser tab.
THE SOURCE IS OPEN
Docs Studio is a real editor with an external surface now. Read the implementation, open the app, or connect your own AI client.