LayerOne (DocX + Sign)

Name: LayerOne (DocX + Sign)
Author: GOLayerone

by GOLayeroneversion 1.0.0i★ –iRuns on your computer

Registry nameio.github.GOLayerone/layerone

Install

Overview

Description from the maker (original English)

MCP server for LayerOne DocX (documents & Factur-X) and Sign (e-signature) APIs.

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs on your computer
Transport: stdio
Category: Other
You need to fill in: DOCX_API_KEY, SIGN_API_KEY

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 1 of 1 passed
Runs on your computer with your user’s permissions (files, network, apps).
You fill in yourself: DOCX_API_KEY, SIGN_API_KEY

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

npmNode.js installed (for the npx command)

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "layerone": {
      "command": "npx",
      "args": [
        "-y",
        "layerone-mcp"
      ],
      "env": {
        "DOCX_API_KEY": "your-value",
        "SIGN_API_KEY": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add layerone --env DOCX_API_KEY=your-value --env SIGN_API_KEY=your-value -- npx -y layerone-mcp

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "layerone": {
      "command": "npx",
      "args": [
        "-y",
        "layerone-mcp"
      ],
      "env": {
        "DOCX_API_KEY": "your-value",
        "SIGN_API_KEY": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "layerone": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "layerone-mcp"
      ],
      "env": {
        "DOCX_API_KEY": "your-value",
        "SIGN_API_KEY": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

DOCX_API_KEY secret required env
DocX API key (documents, PDF, Factur-X). Generate at https://dev.layerone.fr
SIGN_API_KEY secret required env
Sign API key (eIDAS/PAdES e-signature). Generate at https://dev.layerone.fr

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account GOLayerone, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
– Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
– Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
… Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

More stars than 0% of the other 32461 servers in this category
Published to the registry more recently than 13% of the other 32461 servers in this category
Basic checks equal to or better than 100% of the other 32461 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is LayerOne (DocX + Sign) safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: DOCX_API_KEY, SIGN_API_KEY

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.0.0) reached the registry 5 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, dotnet-mcp

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago

Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated yesterday

Install

dotnet-mcp

by Skymly

MCP server for .NET symbols, XAML, source generators, and restricted workspace edit

Runs on your computerUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

LayerOne MCP — DocX + Sign

Serveur MCP (Model Context Protocol) qui expose les API DocX et Sign de LayerOne directement aux agents IA (Claude Desktop, ChatGPT, Cursor, Windsurf, etc.).

Une fois branché, votre assistant IA peut, en langage naturel :

DocX — générer des documents (PDF / DOCX), des factures électroniques Factur-X (réforme 2026), déposer / mettre à jour / télécharger des modèles Word, gérer leur historique de versions, et consulter le quota d'usage.
Sign — envoyer un PDF à la signature électronique eIDAS / PAdES, suivre son statut, vérifier l'identité du signataire par SMS (OTP), télécharger le document signé, récupérer le certificat de preuve et valider l'intégrité cryptographique de la signature.

Installation

Le serveur se lance via npx — aucune installation manuelle requise. Ajoutez le bloc ci-dessous à la configuration MCP de votre client, en renseignant vos deux clés API.

Claude Desktop

Fichier claude_desktop_config.json :

"mcpServers": { "layerone": { "command": "npx", "args": ["-y", "layerone-mcp"], "env": { "DOCX_API_KEY": "votre_cle_docx", "SIGN_API_KEY": "votre_cle_sign" } } } }

Cursor

Fichier ~/.cursor/mcp.json (ou réglages MCP du projet) — même format :

"mcpServers": { "layerone": { "command": "npx", "args": ["-y", "layerone-mcp"], "env": { "DOCX_API_KEY": "votre_cle_docx", "SIGN_API_KEY": "votre_cle_sign" } } } }

ChatGPT / autres clients compatibles MCP

La plupart des clients MCP acceptent la même structure (command = npx, args = ["-y", "layerone-mcp"], env = vos deux clés). Reportez-vous à la documentation MCP de votre client pour l'emplacement exact du fichier de configuration.

Obtenir les clés API

Créez un compte gratuit sur https://dev.layerone.fr, puis générez vos clés dans l'onglet « Clés API » :

une clé DocX → variable d'environnement DOCX_API_KEY ;
une clé Sign → variable d'environnement SIGN_API_KEY.

Le compte gratuit offre 20 documents DocX et 10 signatures Sign par mois.

Les clés ne sont jamais écrites en dur dans le code : elles sont lues uniquement

depuis les variables d'environnement passées par votre client MCP.

Outils exposés

DocX (`https://docx.layerone.fr`)

Outil	Description	Endpoint
`docx_render_facturx`	Générer une facture Factur-X (PDF/A-3)	`POST /render-facturx`
`docx_render_document`	Générer un document PDF ou DOCX	`POST /render-document`
`docx_list_templates`	Lister / filtrer les modèles	`GET /client/templates`
`docx_upload_template`	Déposer un modèle Word	`POST /client/templates`
`docx_update_template`	Mettre à jour un modèle (archive l'ancien)	`PUT /client/templates/{id}`
`docx_download_template`	Télécharger un modèle	`GET /client/templates/{id}`
`docx_delete_template`	Supprimer un modèle	`DELETE /client/templates/{id}`
`docx_list_template_versions`	Lister les versions archivées	`GET /client/templates/{id}/versions`
`docx_download_template_version`	Télécharger une version archivée	`GET /client/templates/{id}/versions/{version_id}`
`docx_restore_template_version`	Restaurer une version archivée	`POST /client/templates/{id}/restore/{version_id}`
`docx_get_usage_stats`	Consulter le quota et l'usage	`GET /usage-stats`

Sign (`https://sign.layerone.fr`)

Outil	Description	Endpoint
`sign_send_for_signature`	Envoyer un PDF à signer	`POST /v1/documents/send`
`sign_detect_fields`	Détecter les champs de signature ([[...]])	`POST /v1/documents/detect-fields`
`sign_get_document_status`	Consulter le statut d'une signature	`GET /v1/documents/{id}`
`sign_download_signed_document`	Télécharger le PDF signé	`GET /v1/documents/{id}/download`
`sign_send_otp`	Envoyer un code OTP par SMS	`POST /v1/otp/request`
`sign_verify_otp`	Vérifier le code OTP	`POST /v1/otp/verify`
`sign_validate_signature`	Vérifier l'intégrité de la signature	`GET /v1/documents/{id}/validate`
`sign_get_audit_certificate`	Récupérer le certificat de preuve	`GET /v1/documents/{id}/audit`
`sign_cancel_document`	Annuler une demande de signature	`DELETE /v1/documents/{id}`

Fichiers : les modèles et PDF sont fournis aux outils encodés en base64

(template_base64, pdf_base64). Pour les téléchargements, le serveur renvoie un

résumé (taille + aperçu base64 tronqué) plutôt que le binaire complet, afin de ne

pas saturer la conversation.

Développement local

cd integrations/mcp

npm install npm run build # compile src/ → dist/ DOCX_API_KEY=... SIGN_API_KEY=... node dist/index.js

Le serveur communique sur stdio (entrée/sortie standard) selon le protocole MCP.

Publication

npm : publication automatique avec provenance via .github/workflows/publish.yml (déclenché par une release GitHub).
MCP Registry : le manifeste server.json (champ name io.github.GOLayerone/layerone, identique au mcpName de package.json) permet la publication au registre officiel via l'outil mcp-publisher.

LayerOne (DocX + Sign)

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

Values you fill in

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Otheri

Common questions

Alternatives

Spec Driven Development

Remote Desktop Commander

dotnet-mcp

README from the maker

LayerOne MCP — DocX + Sign

Installation

Claude Desktop

Cursor

ChatGPT / autres clients compatibles MCP

Obtenir les clés API

Outils exposés

DocX (https://docx.layerone.fr)

Sign (https://sign.layerone.fr)

Développement local

Publication

Licence

DocX (`https://docx.layerone.fr`)

Sign (`https://sign.layerone.fr`)