Skip to main content

MCP server exposing the AFNOR XP Z12-013 APIs for French electronic invoicing (Compatible Solution)

Project description

mcp-facture-electronique-fr 🇫🇷

English | Francais

License PyPI version Python mcp-facture-electronique-fr MCP server

A Python MCP server exposing the standardized AFNOR XP Z12-013 APIs for the French e-invoicing reform (effective September 1, 2026). This project enables AI agents (Claude, IDEs) to interact natively with the Approved Platform (PA/PDP) ecosystem as a Compatible Solution (SC).

Built on

This package is built on top of mcp-einvoicing-core, a shared base library for European e-invoicing MCP servers. It provides the OAuth2 HTTP client, token cache, shared models, logging utilities, and exception hierarchy used by this package.

mcp-einvoicing-core is installed automatically as a transitive dependency, no extra step is needed.

For contributors: pip install -e ".[dev]" installs the base package from PyPI automatically.


Scope (Compatible Solution)

This server operates in Compatible Solution (CS) mode as defined by the French e-invoicing reform. The CS acts as an intermediary between the company's information system and an Approved Platform (AP/PDP). This means:

  • No profile validation of caller-supplied payloads. The server transmits the invoice file (Factur-X PDF/A-3, UBL 2.1, or CII XML) as provided. Structural and business-rule validation (NF XP Z12-012 profiles, Schematron rules) is performed by the receiving Approved Platform, not by this server.
  • No e-reporting payload validation beyond schema-level XSD. Transaction reports (Flux 10.1/10.3) and payment reports (Flux 10.2/10.4) are validated against the DGFiP v3.2 XSD schema when validate_ereporting_xml is called, but deeper business-rule checks (e.g. coherence between declared amounts and invoice totals) are the responsibility of the AP.
  • No PDF/A-3 envelope generation. The caller must produce the conformant Factur-X PDF/A-3 file with embedded CII XML. This server transmits the finished binary.

The Approved Platform performs final validation and may reject non-conformant submissions with an error code and message.


🏗️ Architecture

The server acts as an intelligent communication interface between your AI agent and the technical infrastructure of the reform:

[ ERP / Business IS ] <--> [ MCP Server ] <--> [ Approved Platform (PA/PDP) ]
          ^                        |
          |                        v
   [ AI Agent (Claude) ] <--- (XP Z12-013 Standard)

🛠️ Exposed services

Service Domain Standard MCP Tools
Flow Service Invoice flows and e-reporting Annex A, v1.2.0 5 tools
PPF Annuaire (directory) Central directory (SIREN/SIRET/routing/addressing) PPF swagger v1.11.0 20 tools
Webhook Service Event notification subscriptions Annex A, v1.2.0 5 tools
Factur-X Service CII XML validation (Schematron) Factur-X 1.08 1 tool

Text bumped to June 2026 (v1.2.0 swagger current) — AFNOR resupplied the XP Z12-013 narrative text in June 2026 without an updated swagger; the server continues to implement the v1.2.0 wire contract.

Note (FR-XSLT2-1, resolved): the bundled Factur-X 1.08 Schematron stylesheets require XSLT 2.0, which lxml/libxslt (XSLT 1.0 only) cannot compile — the same root cause as the DE-XSLT2-1 gap tracked for ZUGFeRD. validate_facturx now runs real Schematron validation via Saxon-HE. Install the optional xslt2 extra for this to work: pip install mcp-facture-electronique-fr[xslt2]. Without it, the tool degrades gracefully to level="unavailable".

Note (FR-FLUX11-2026-06, PPF Annuaire): the directory tools are wired directly against the bundled PPF-platform swagger ppf-openapi-annuaire-api-public-1.11.0-openapi.json — this is a PPF-platform-specific interface, not a PDP-agnostic Annex B abstraction. Per the swagger's own description, these endpoints are subject to change and require prior PISTE application publication before use.

🚀 Installation

Via PyPI (recommended)

pip install mcp-facture-electronique-fr

Or without prior installation using uvx:

uvx mcp-facture-electronique-fr

For Factur-X Schematron validation (validate_facturx, requires the XSLT 2.0 / Saxon-HE backend — see FR-XSLT2-1 above):

pip install mcp-facture-electronique-fr[xslt2]

From source

# Clone the repository
git clone https://github.com/cmendezs/mcp-facture-electronique-fr.git
cd mcp-facture-electronique-fr

# Create the virtual environment
python -m venv .venv
source .venv/bin/activate  # On Windows: .venv\Scripts\activate

# Install in editable mode
pip install -e ".[dev]"
# Initial configuration
cp .env.example .env
# Edit .env with the credentials provided by your PA/PDP

⚙️ Configuration (.env)

The server requires the following variables to authenticate with an Approved Platform (PA):

Variable Description
PA_BASE_URL_FLOW Base URL of the PA Flow Service
PA_BASE_URL_DIRECTORY Deprecated — no longer read; see PPF_ANNUAIRE_BASE_URL
PPF_ANNUAIRE_BASE_URL Base URL of the PPF Annuaire service (defaults to the production swagger servers URL; override for sandbox testing)
PA_CLIENT_ID OAuth2 Client ID
PA_CLIENT_SECRET OAuth2 Client Secret
PA_TOKEN_URL Authentication server URL
PA_ORGANIZATION_ID Organization identifier for multi-tenant AP (optional)
HTTP_TIMEOUT Request timeout (default: 30s)
PPF_GLOBAL_ID PPF party GlobalID for the CDAR second RecipientTradeParty (optional; unset by default, see submit_lifecycle_status)
PPF_SCHEME_ID schemeID for PPF_GLOBAL_ID (default 0238)
PPF_NAME Name for the PPF RecipientTradeParty (default PPF)
PPF_ROLE_CODE RoleCode for the PPF RecipientTradeParty (default DFH)

🤖 Claude Desktop integration

To use this server with Claude, add this configuration to your claude_desktop_config.json file:

{
  "mcpServers": {
    "facture-electronique-fr": {
      "command": "uvx",
      "args": ["mcp-facture-electronique-fr"],
      "env": {
        "PA_BASE_URL_FLOW": "https://api.votre-pdp.fr/flow",
        "PPF_ANNUAIRE_BASE_URL": "https://aife.economie.gouv.fr/ppf/annuaire-public/v1",
        "PA_CLIENT_ID": "votre-id",
        "PA_CLIENT_SECRET": "votre-secret",
        "PA_TOKEN_URL": "https://auth.votre-pdp.fr/oauth/token"
      }
    }
  }
}

⌨️ Cursor integration

Cursor supports MCP servers via stdio. Add the configuration in:

  • Global (all projects): ~/.cursor/mcp.json
  • Project (this repository only): .cursor/mcp.json
{
  "mcpServers": {
    "facture-electronique-fr": {
      "command": "uvx",
      "args": ["mcp-facture-electronique-fr"],
      "env": {
        "PA_BASE_URL_FLOW": "https://api.votre-pdp.fr/flow",
        "PPF_ANNUAIRE_BASE_URL": "https://aife.economie.gouv.fr/ppf/annuaire-public/v1",
        "PA_CLIENT_ID": "votre-id",
        "PA_CLIENT_SECRET": "votre-secret",
        "PA_TOKEN_URL": "https://auth.votre-pdp.fr/oauth/token"
      }
    }
  }
}

Reload the Cursor window (Ctrl+Shift+P then Reload Window) to apply the changes.

🪐 Kiro integration

Kiro supports MCP servers via its dedicated configuration file. Two levels are available:

  • Global (all projects): ~/.kiro/settings/mcp.json
  • Workspace (this repository only): .kiro/settings/mcp.json
{
  "mcpServers": {
    "facture-electronique-fr": {
      "command": "uvx",
      "args": ["mcp-facture-electronique-fr"],
      "env": {
        "PA_BASE_URL_FLOW": "https://api.votre-pdp.fr/flow",
        "PPF_ANNUAIRE_BASE_URL": "https://aife.economie.gouv.fr/ppf/annuaire-public/v1",
        "PA_CLIENT_ID": "votre-id",
        "PA_CLIENT_SECRET": "votre-secret",
        "PA_TOKEN_URL": "https://auth.votre-pdp.fr/oauth/token"
      },
      "disabled": false,
      "autoApprove": []
    }
  }
}

The file is automatically reloaded on save. You can also open the config via the command palette (Cmd+Shift+P / Ctrl+Shift+P) then MCP.

Kiro security tip: rather than writing secrets in plain text, use the syntax "PA_CLIENT_SECRET": "${PA_CLIENT_SECRET}", Kiro resolves shell environment variables at startup.

🧰 Available MCP tools

Flow Service (Flow management)

  • submit_flow: Submit invoices (Factur-X, UBL, CII) or e-reporting data.
  • search_flows: Multi-criteria search of sent or received flows using the standard filters.
  • submit_lifecycle_status: Update the lifecycle status (e.g., Made available, Collected, Dispute).
  • get_flow: Retrieve the full details and attachments of a specific flow.
  • healthcheck_flow: Test the connectivity and availability of the PA Flow API.

PPF Annuaire (directory)

Wired directly against the bundled PPF-platform swagger ppf-openapi-annuaire-api-public-1.11.0-openapi.json — see the note above.

  • search_company / get_company_by_siren / get_company_by_id_instance: Look up legal units (SIREN).
  • search_establishment / get_establishment_by_siret / get_establishment_by_id_instance: Look up establishments (SIRET).
  • search_routing_code / get_routing_code_by_siret_and_code / get_routing_code_by_id_instance / create_routing_code / update_routing_code / replace_routing_code: Manage routing codes (code-routage).
  • search_directory_line / get_directory_line_by_code / get_directory_line / create_directory_line / update_directory_line / replace_directory_line / delete_directory_line: Manage directory lines (ligne-annuaire), the electronic-invoice receiving addresses.
  • check_ppf_annuaire_health: Check availability of the PPF Annuaire service.

Webhook Service (Webhook management)

  • list_webhooks: List all webhook subscription IDs for the current token holder.
  • get_webhook: Retrieve the full details of a webhook subscription.
  • create_webhook: Subscribe to flow event notifications (filter by flow type, direction, processing rule).
  • update_webhook: Update a webhook's technical parameters (authentication, signature).
  • delete_webhook: Unsubscribe from a webhook.

📚 Regulatory references

  • AFNOR XP Z12-012: Invoice message formats, profiles, and lifecycle statuses (v1.4, June 2026 edition).
  • AFNOR XP Z12-013: Service interface specifications (June 2026 edition; v1.2.0 wire contract).
  • AFNOR XP Z12-014: Technical implementation guide for business use cases (v1.4, June 2026 edition).
  • France B2B reform: Mandatory rollout schedule (2024-2026).

🧪 Tests

# Run the unit and integration test suite
pytest tests/ -v

Other e-invoicing MCP servers

Country Server
🌍 Global mcp-einvoicing-core
🇧🇪 Belgium mcp-einvoicing-be
🇧🇷 Brazil mcp-nfe-br
🇫🇷 France mcp-facture-electronique-fr
🇩🇪 Germany mcp-einvoicing-de
🇮🇹 Italy mcp-fattura-elettronica-it
🇵🇱 Poland mcp-ksef-pl
🇪🇸 Spain mcp-facturacion-electronica-es

📄 License

This project is distributed under the Apache 2.0 license. See the LICENSE file for details.


Project maintained by cmendezs. For any questions about the XP Z12-013 standard implementation, feel free to open an Issue.

Project details


Download files

Download the file for your platform. If you're not sure which to choose, learn more about installing packages.

Source Distribution

mcp_facture_electronique_fr-0.8.0.tar.gz (340.3 kB view details)

Uploaded Source

Built Distribution

If you're not sure about the file name format, learn more about wheel file names.

mcp_facture_electronique_fr-0.8.0-py3-none-any.whl (248.7 kB view details)

Uploaded Python 3

File details

Details for the file mcp_facture_electronique_fr-0.8.0.tar.gz.

File metadata

File hashes

Hashes for mcp_facture_electronique_fr-0.8.0.tar.gz
Algorithm Hash digest
SHA256 1a9b5eeab29cf9e29fa7b7b1ede09890fdeff48e8d36df9460f48d89c777b000
MD5 cc0973cdc2efeb365c343c3b70f27741
BLAKE2b-256 7826725765f53b833a49653fd4ecd17978de61bfd4e2807918e607e516fee05f

See more details on using hashes here.

Provenance

The following attestation bundles were made for mcp_facture_electronique_fr-0.8.0.tar.gz:

Publisher: publish.yml on cmendezs/mcp-facture-electronique-fr

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

File details

Details for the file mcp_facture_electronique_fr-0.8.0-py3-none-any.whl.

File metadata

File hashes

Hashes for mcp_facture_electronique_fr-0.8.0-py3-none-any.whl
Algorithm Hash digest
SHA256 97928dd2b90947e588f8d9f51af914ba5166f5102f6f208031649639f257dc6d
MD5 703a0a6ffee44e9f4550fd2978c52a1a
BLAKE2b-256 1e27d44d8c63db7a986e531c423eba1c97d532d68a46677cb4610fe73260aacb

See more details on using hashes here.

Provenance

The following attestation bundles were made for mcp_facture_electronique_fr-0.8.0-py3-none-any.whl:

Publisher: publish.yml on cmendezs/mcp-facture-electronique-fr

Attestations: Values shown here reflect the state when the release was signed and may no longer be current.

Supported by

AWS Cloud computing and Security Sponsor Datadog Monitoring Depot Continuous Integration Fastly CDN Google Download Analytics Pingdom Monitoring Sentry Error logging StatusPage Status page