Living Docs MCP
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Living Docs MCPCreate a shared live document for our team to brainstorm project ideas."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Living Docs for your agent
Create live, shared interactive documents with the AI you already use. Connect your account, describe what you need, and let your agent build it with you.
Status — September 6, 2026: The plugins and release downloads are published, and the local stdio setup has been tested. Hosted connection activation is pending publisher dashboard sign-in and a completed OAuth connection test. For a setup you can use now, follow the local stdio instructions.
The hosted MCP address is:
https://living-docs-workspace.vercel.app/mcpThe plugin in plugins/living-docs/ combines that connection with authoring guidance,
SDK documentation, working examples, and app installation guidance. It includes
Claude Code, Codex, and Agent Plugins 1.0 manifests. The hosted connection uses
your Living Docs sign-in; the plugin contains no credentials.
Start at the setup guide, or use the client instructions in this repository.
For Claude Code, install the connection and skill together:
claude plugin marketplace add https://github.com/s2bomb/living-docs-connect.git
claude plugin install living-docs@living-docs-connectOpen Claude Code, run /mcp, and sign in to Living Docs. Start a new session if
the skill is not listed yet.
For Codex, install the plugin from this repository's marketplace:
codex plugin marketplace add https://github.com/s2bomb/living-docs-connect.git
codex plugin add living-docs@living-docs-connectComplete the connection's sign-in prompt and start a new task. If your Codex version does not offer plugins, the MCP-only setup works through its MCP configuration.
Then try:
Use Living Docs to make a shared shopping list for my household. Help me get the main interaction working first, then improve how it looks.
Public directory listings require each vendor's review. A custom MCP connection or this repository's plugin marketplace does not require a Living Docs listing in those directories.
Downloads and updates
The v0.4.0 release contains:
living-docs-skill-0.4.0.zip: a standalone skill for Claude chat and other clients that accept Agent Skills.living-docs-plugin-0.4.0.zip: the plugin folder for a local installation.s2bomb-living-docs-mcp-0.4.0.tgz: the optional local stdio server, requiring Node.js 22 or newer. The hosted setup does not require Node.js.SHA256SUMS: hashes for checking downloaded artifacts.
Hosted server fixes roll out at the same URL. Installed skills and plugin metadata follow the client's update process. See updates.
Related MCP server: Maticon Office DocSpace MCP Server
Package contents
The same skill directory is shared by the native Claude Code and Codex manifests
and the portable Agent Plugins 1.0 manifest. Claude Code and Codex share the native
.mcp.json; the portable format uses its required mcp.json. Each contains only
the hosted endpoint, while each client manages OAuth and its own credentials.
This repository contains the deliberate distribution package and public docs. Report a problem through GitHub issues, with the client version and error message. Remove credentials and document contents from reports.
Maintaining a release
For maintainers, npm ci && npm test checks the portable schemas, native manifest
contracts, shared skill references, and credential-free package contents.
See release preparation and the
directory submission checklist.
The distribution strategy explains the client
priorities, evidence, and packaging choices.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
No tool schema history has been recorded yet.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
Persistent docs and memory for AI agents — read, write, organize & search a shared workspace.
- OneLoreOAuthai.onelore
Shared project context for AI agents and teams: docs, tasks, and messages that stay current.
Connect your agent to branchly: manage content, prompts, actions, learn from analytics and insights
Connect AI agents to 1000+ apps with managed authentication and tool-calling.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceConnects Claude to Google Docs, allowing users to list, read, create, update, search, and delete documents in their Google Drive through natural language interactions.1,3031MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to manage rooms, collaborate on files, set permissions, and automate document workflows in Maticon Office DocSpace using natural language commands.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to securely interact with Google Workspace services, including sending emails via Gmail and appending content to Google Docs.225MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to send emails via Gmail and append content to Google Docs.225MIT
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/s2bomb/living-docs-connect'
If you have feedback or need assistance with the MCP directory API, please join our Discord server