Productivity · Local MCP server
LayerOne (DocX + Sign)
MCP server for LayerOne DocX (documents & Factur-X) and Sign (e-signature) APIs.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.GOLayerone/layerone- Version
- 1.0.0
- Status
- Active
- Category
- productivity
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-06-18
- Updated
- 2026-06-18
- Publisher
- GOLayerone (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/GOLayerone) · how
- Website
- dev.layerone.fr
- Repository
- github.com/GOLayerone/layerone-mcp
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | layerone-mcp | 1.0.0 | stdio |
How to connect LayerOne (DocX + Sign)
LayerOne (DocX + Sign) runs locally from a Node.js package published to the npm registry: layerone-mcp version 1.0.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y layerone-mcp@1.0.0. It reads these environment variables: DOCX_API_KEY (required, secret) and SIGN_API_KEY (required, secret); set them in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"layerone": {
"command": "npx",
"args": [
"-y",
"layerone-mcp@1.0.0"
],
"env": {
"DOCX_API_KEY": "<secret>",
"SIGN_API_KEY": "<secret>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More productivity servers
| Server | Runs |
|---|---|
| Laver MCPKanban boards, sprints, tickets and a team wiki, with versioned writes for concurrent agents. | Local · stdio |
| Lawmatics MCPConnect Claude to Lawmatics: matters, contacts, pipelines, tasks, forms, custom fields, invoices. | Local · stdio |
| LaxisSearch and read your Laxis meeting transcripts, AI summaries, and participants from Claude. | Remote · HTTPLive check: sign-in required |
| LayerCallScore an IP, email, phone, domain or device for fraud in one call, with the signals behind it. | Remote · HTTPLive check: ✓ handshake |
| Layers Marketing MCPGive your agent marketing superpowers: research, renders, delivery, paid campaigns, measurement. | Remote & Local · HTTP, stdioLive check: sign-in required |
| Lead FriendlyAI phone calls, SMS and CRM records in one Lead Friendly account, compliance-checked on every send. | Remote · HTTPLive check: sign-in required |
| Lead Generation MCPB2B and local lead gen: verified emails, site contacts, Maps and Yellow Pages leads. | Remote · HTTPLive check: sign-in required |
| Lead IntelligenceAnalyze and score leads to identify high-potential prospects and prioritize sales outreach. | Remote · HTTPLive check: sign-in required |