MCP.Market

Living Docs MCP server

online · 100% uptime
by s2bomb·io.github.s2bomb/living-docs·v0.4.0

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

A92/100grade A
What users say
No reviews yet
Be the first
Safety scan
A92/100

full report

Adoption
New

0 stars

Reviews

Write one

Nobody has reviewed Living Docs yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Living Docs tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Public scan report

scanner v0.1.10 · 2026-10-16 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 1798ms (auth required)20/20
  • –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
  • Auth qualityOAuth resource metadata advertised on 40115/15
  • Maintenancelast push 40 days ago12/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 92/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Living Docs compares

Against every graded Productivity MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
92/100
higher than 90% of 1,301 Productivity servers
Uptime
100%
of our recent checks; the typical remote Productivity server answers 100%
Response time
2,022 ms
faster than 5% of 656 Productivity servers

Install Living Docs in Claude Code, Cursor or VS Code

claude mcp add --transport http living-docs https://living-docs-workspace.vercel.app/mcp
Add to Cursor

What the publisher says

From the Living Docs repository's README, as published. We do not edit it. Read it on GitHub

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:

clients that accept Agent Skills.

  • living-docs-skill-0.4.0.zip: a standalone skill for Claude chat and other

Node.js 22 or newer. The hosted setup does not require Node.js.

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

Nothing above is checked by us. What we check is on the safety report.

Living Docs: common questions

Is Living Docs MCP server safe?
Yes, by our scan: it is graded A (92/100). Read the Living Docs safety report
How do I install Living Docs?
It runs remotely at living-docs-workspace.vercel.app. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Living Docs need an API key?
No key to paste: it signs you in with OAuth when your client connects.
Is Living Docs maintained?
The last commit was 61 days ago (2026-09-06). The latest release is v0.4.0.
Is Living Docs up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
What can I use instead of Living Docs?
Servers from other publishers that do the same job: Livewire Flux MCP server, Context7 MCP server and Svelte MCP server.
How does Living Docs compare with other Productivity MCP servers?
safety score 92/100 (higher than 90% of 1,301 Productivity servers); uptime 100% (of our recent checks; the typical remote Productivity server answers 100%); response time 2,022 ms (faster than 5% of 656 Productivity servers). Full comparison.

Alternatives to Living Docs

Same job from other publishers: the closest match first, then the best rated.

  • Livewire Flux
    Flux UI component and layout docs for AI coding agents. Live from fluxui.dev, Pro-tier aware.
    A
  • Context7
    Up-to-date docs for AI agents
    A
  • Svelte MCP
    The official Svelte MCP server providing docs and autofixing tools for Svelte development
    A
  • SvGrid
    Checks AI-written SvGrid code against the real API, plus version-pinned Svelte 5 grid docs.
    A
  • Coolify
    46 optimized tools for managing Coolify infrastructure, diagnostics, and docs search
    B