English Français العربية

Living Docs

Official registry Productivity

Create and improve live, shared interactive documents with your agent.

Source code Website Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code 
claude mcp add --transport http living-docs 'https://living-docs-workspace.vercel.app/mcp'
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "living-docs": {
            "type": "http",
            "url": "https://living-docs-workspace.vercel.app/mcp"
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. Living Docs for your agent
  2. Downloads and updates
  3. Package contents
  4. Maintaining a release

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 hosted MCP passed SDK OAuth, token refresh, and tool checks, plus native Codex plugin installation and sign-in. The public local stdio release passed a fresh Claude Code document-building test. See the validation record for the scope and remaining client checks.

The hosted MCP address is:

https://living-docs-workspace.vercel.app/mcp

The 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-connect

Open 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-connect

Complete 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.

The hosted endpoint is listed in the MCP Registry. Curated client directories 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.

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.

Frequently asked questions

What is Living Docs?

Create and improve live, shared interactive documents with your agent.

How do I install Living Docs?

It runs as a remote server. In Claude Code: claude mcp add --transport http living-docs 'https://living-docs-workspace.vercel.app/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does Living Docs need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is Living Docs open source?

Its code is public on GitHub, but the repository does not declare a standard license.

Who maintains Living Docs?

It is published by s2bomb. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.