LayerOne (DocX + Sign) vs Outline MCP Server
LayerOne (DocX + Sign) is an MCP server published by GOLayerone. Marketplaces we read that list it: 1 (Official MCP Registry). Outline MCP Server is an MCP server published by Vortiago. Marketplaces we read that list it: 3 (Official MCP Registry, Claude Code: claude-plugins-community, Community GitHub marketplaces). As of our marketplace pass on 2026-10-19. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace | ||
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.0 Downloads/month (npm): 137 Downloads/week (npm): 25 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 1.10.1 Downloads/month (PyPI): 1 398 Downloads/week (PyPI): 337 Forks (GitHub): 45 Stars (GitHub): 156 Not marked · First seen |
| Claude Code: claude-plugins-community | Not listed | Listed Version: 1.10.1 Forks (GitHub): 45 Stars (GitHub): 156 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | LayerOne (DocX + Sign) | Outline MCP Server |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 3 (better) |
| Stars (GitHub) (differs) | 0 (worse) | 156 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 45 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (layerone-mcp) | On your machine (mcp-outline) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 2 | 6, secrets among them: 1 |
| Parts of the bundle (differs) | Not a bundle | 3 |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/golayerone/layerone-mcp | github.com/vortiago/mcp-outline |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen | 2026-10-11 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
LayerOne (DocX + Sign)
MCP server for LayerOne DocX (documents & Factur-X) and Sign (e-signature) APIs.
Outline MCP Server
Connect AI assistants to Outline for document search, reading, and management
How to run each
LayerOne (DocX + Sign) As a local MCP server: npm package
claude mcp add --env "DOCX_API_KEY=<YOUR_DOCX_API_KEY>" --env "SIGN_API_KEY=<YOUR_SIGN_API_KEY>" --transport stdio layerone -- npx -y layerone-mcp
Requires: DOCX_API_KEY (secret), SIGN_API_KEY (secret)
Outline MCP Server As a local MCP server: PyPI package
claude mcp add --env "OUTLINE_API_KEY=<YOUR_OUTLINE_API_KEY>" --transport stdio mcp-outline -- uvx mcp-outline
Requires: OUTLINE_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Only LayerOne (DocX + Sign) asks for
DOCX_API_KEY (secret)SIGN_API_KEY (secret)
Only Outline MCP Server asks for
OUTLINE_API_KEY (secret)OUTLINE_API_URLOUTLINE_DISABLE_AI_TOOLSOUTLINE_DISABLE_DELETEOUTLINE_READ_ONLYOUTLINE_VERIFY_SSL
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: LayerOne (DocX + Sign) · What it can do: Outline MCP Server · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.