Living Docs

io.github.s2bombPublished by GitHub account s2bombv0.4.0Updated Oct 24, 2026

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

VerifiedStreamable HTTPWeb executableProductivity & WorkflowCommunication & Collaboration

Overview

AI-generated overview

Hosted MCP server that lets an assistant build and refine live, shared interactive documents inside a Living Docs account.

What you can do
  • Create live, shared interactive documents with the assistant, starting from a plain description of what is needed.
  • Iterate on a document with the agent, for example getting the main interaction working before improving its appearance.
  • Share the resulting documents with other people, such as a household shopping list.
  • Connect through a hosted endpoint or an optional local stdio server, with authoring guidance and examples supplied by the plugin.
When to use it
Useful when you want an assistant to help you author and iterate on interactive, shareable documents rather than static text, and you are comfortable signing in to a Living Docs account.
Requirements
A remote endpoint at the provider's hosted address, or the optional local stdio package, which requires Node.js 22 or newer; the hosted setup does not need Node.js. OAuth sign-in to a Living Docs account is required. Client-side plugin installation is optional.
Before you install
The connection uses your Living Docs sign-in, so the assistant acts under your account; the plugin itself contains no credentials and each client manages OAuth. Documents you create are shared, so check who can see them. Remove credentials and document contents before reporting problems.

Installation

In SourceWeft

  1. Open Living Docs in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.s2bomb%2Fliving-docs/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "living-docs": {
      "type": "http",
      "url": "https://living-docs-workspace.vercel.app/mcp"
    }
  }
}

README

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:

text
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:

sh
claude plugin marketplace add https://github.com/s2bomb/living-docs-connect.gitclaude 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:

sh
codex plugin marketplace add https://github.com/s2bomb/living-docs-connect.gitcodex 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.

Source: README.md at commit d09e7a8

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.4.0LatestSep 16, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.