
Facturx Toolkit
io.github.CedricKoumaPublished by GitHub account CedricKoumav0.1.0Updated Oct 24, 2026
Validate, extract, repair and generate French Factur-X / EN16931 invoices via AgentForge API
Overview
A remote or local MCP server that lets an assistant validate, extract, repair and generate French Factur-X / EN16931 electronic invoices through the AgentForge.
- What you can do
- Validate French Factur-X / EN16931 invoices against the standard's rules and report errors or non-conformities. Extract structured invoice data from existing Factur-X documents. Repair invoices that fail validation so they conform to the standard. Generate new Factur-X / EN16931 invoices from supplied data. All operations run through the AgentForge API gateway rather than locally.
- When to use it
- Use it when you work with French electronic invoicing and need an assistant to check, read, fix or produce Factur-X / EN16931 compliant invoices, for example during e-invoicing compliance work or when converting invoice data into the required format.
- Requirements
- Either the remote endpoint or the local npm package agentforge-facturx-mcp (Node.js, stdio). An AgentForge APIM subscription key is required, supplied as the Ocp-Apim-Subscription-Key header or the AGENTFORGE_API_KEY environment variable. The AGENTFORGE_BASE_URL variable can point to the gateway base URL. Network access to the AgentForge gateway is needed.
Installation
In SourceWeft
- Open Facturx Toolkit in the dashboard and add it to a workspace.
- Connect Ocp-Apim-Subscription-Key credentials. They are stored privately and never shown on public pages.
- 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.CedricKouma%2Ffacturx-toolkit/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.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"facturx-toolkit": {
"type": "http",
"url": "https://apim-agentforge-6lfm33.azure-api.net/facturx/mcp",
"headers": {
"Ocp-Apim-Subscription-Key": "<YOUR_API_KEY>"
}
}
}
}Tools
0Version history
1- v0.1.0LatestSep 16, 2026
Score
60% 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
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.