Beta · Pilot program open

Index — Plateforme MCP × ERP

Your ERPs.Your agents.One MCP protocol.

ERP Platform speaks MCP to the agent and adapter to the ERP. Systems stay where they are, agents call structured tools. Auth, secrets and audit are handled once — not per ERP.

Read the docs

Adapters

2 + N

erpnext · dolibarr · *

Tenant model

multi

DEK · AES-GCM

Runtime

2 modes

direct · tunnel

ERP-agnostic ✕ MCP-native ✕ Secrets isolés ✕ Tunnel sortant ✕ Audit horodaté

Compatible with / Agents

Claude, ChatGPT, Cursor, Windsurf, Goose — one protocol, your ERPs on the other side.

  • ClaudeClaude
  • OpenAIOpenAI
  • CursorCursor
  • WindsurfWindsurf
  • GooseGoose
  • ClaudeClaude
  • OpenAIOpenAI
  • CursorCursor
  • WindsurfWindsurf
  • GooseGoose
  • ClaudeClaude
  • OpenAIOpenAI
  • CursorCursor
  • WindsurfWindsurf
  • GooseGoose

Architecture

Une plateforme posée sur la
stack Casys MCP.

Four open-source bricks assembled under a single tenant: server, bridge, dashboards, adapters.

  1. 01

    Agent IA

    ▸ MCP

    Claude.ai, ChatGPT, Cursor

    tools/list ▸ tools/call

  2. 02

    Tenant edge

    ▸ Stable

    Un endpoint MCP par client

    acme.erp-platform.fr · AES-GCM/DEK · audit

  3. 03

    Bridge

    ▸ Stack

    Direct, ou pont sortant chez le client

    @casys/mcp-bridge · LAN, VPN, firewall — sans port entrant

  4. 04

    Adapter

    ▸ Core

    Contrat ERP-agnostic

    @casys/mcp-erp · ERPNext, Dolibarr, *

  5. 05

    ERP

    ▸ Cible

    Le système métier

    API hosted · LAN · legacy

// Casys MCP stack

  • @casys/mcp-serverCore

    MCP server foundation. Transports, middleware, OAuth/JWT, resources, metrics, MCP Apps primitives.

  • @casys/mcp-bridgeBridge

    Bridge brick. Connects MCP Apps to external channels. Outbound tunnel for the local bridge process.

  • @casys/mcp-composeDashboards

    MCP screen composition. Multi-pane layouts, inter-view sync, shared viewers.

  • @casys/mcp-erpAdapter

    ERP-agnostic adapter contract. Plug ERPNext, Dolibarr and the rest without rebuilding the rest.

  • mcp-einvoiceExtension

    E-invoicing extension. Wired to ERP data when the invoice workflow needs it.

ERPs supportés

Un contrat ERP.
N adapters derrière.

Le contrat est dans @casys/mcp-erp. ERPNext aujourd'hui, Dolibarr en cours. Pour les autres, on évalue ensemble.

Stable

GA

Profondeur prouvée — en pilote.

ERPNext

Adapter le plus mature. Lecture, écriture, validation. Sert de référence pour la profondeur attendue.

@casys/mcp-erpnext

En cours

WIP

Adapter en mapping progressif.

Dolibarr

Scaffold adapter en place. Mapping des entités factures/clients/articles en cours.

@casys/mcp-erp/dolibarr

Roadmap

OPEN

Couverts par le contrat adapter.

Votre ERP

SAP, Sage, Odoo, NetSuite, ERP métier interne. On évalue le scope du pilote ensemble.

demande-le

// adapter contract : @casys/mcp-erp

Runtime

ERP en ligne.
Ou ERP en local, via tunnel.

Depending on where your ERP lives — cloud, hosted, or installed inside your LAN — we pick the connection mode. Tunnel mode is a guided pilot today.

Direct mode

GA

ERP reachable through an API

ERPNext Cloud, hosted Frappe, public Dolibarr, any ERP with an open API. Connectors execute on the platform side.

  1. [01]Agent calls the customer's MCP endpoint
  2. [02]ERP Platform validates tenant, session, action
  3. [03]Connector calls the hosted ERP API
  4. [04]Structured response back to the agent

The ERP secret stays on the platform — outside the prompt and the MCP client.

Tunnel mode

PILOTE

ERP behind a firewall

Dockerised ERPNext, LAN Dolibarr, on-prem ERP. A small bridge process runs at the customer and opens an outbound connection through the bridge.

  1. [01]Outbound bridge enrolled at the customer (lightweight process)
  2. [02]Outbound WebSocket to the ERP Platform relay
  3. [03]Agent calls MCP, ERP Platform routes to the right tenant
  4. [04]Execution inside the LAN against localhost / LAN / VPN

No inbound port. Only the bridge establishes an outbound connection. Guided pilot mode — not self-service yet.

Workflow

Quatre étapes.
Aucun secret dans le prompt.

An agent call crosses the platform without ever seeing your ERP credentials. Every step leaves a trace.

  1. [01]Step 01

    Isolated tenant

    One subdomain per customer. Encrypted keys. ERP config scoped.

    host    →  acme.erp-platform.fr
tenant  →  resolved
dek     →  loaded · AES-GCM
  2. [02]Step 02Core

    ERP adapter

    ERPNext today. Dolibarr in progress. Same contract throughout.

    adapter →  erpnext
tools   →  invoice.list, item.get, …
contract → @casys/mcp-erp v0
  3. [03]Step 03

    AI agent

    Claude or your agent calls MCP tools. No API key transits.

    agent   →  Claude / ChatGPT / *
rpc     →  tools/call invoice.list
scope   →  tenant: acme
  4. [04]Step 04

    Audit

    Tenant, target ERP, mode, result. Timestamped. Actionable in support.

    trace   →  2026-05-19T08:42:17Z
tenant  →  acme
result  →  ok · 47 rows
// call trace · per tenant · timestampedend of sequence ▮

E-invoicing

L'ERP alimente.
La conformité reste séparée.

ERP Platform is neither a PA nor a PDP. mcp-einvoice takes over for issuing and receiving.

E-invoicing = extension. Wire it through the Casys e-invoicing components when the workflow demands it.

ERP data

Customers, items, invoices stay in the source ERP. The adapter exposes only what's needed.

Compliance layer

mcp-einvoice carries the tools, viewers and adapters to PA/PDP providers.

Agentic composition

An agent prepares, verifies, follows up. The ERP does not become an approved platform — mcp-einvoice does.

// Pipeline e-invoicing

step 1 → 4
  1. [01]Source ERP
  2. [02]MCP adapter
  3. [03]eInvoice workflow
  4. [04]PA / PDP

Why this layer

Le bon étage entre vos ERP
et vos agents.

A reliable execution interface between existing business systems and AI agents.

[01]

ERP-agnostic

The pivot is the adapter. Adding an ERP touches neither multi-tenancy, nor auth, nor audit.

adapters: ["erpnext", "dolibarr", "..."]
[02]

MCP-native

Agents consume structured MCP tools, not an ad-hoc REST layer.

tools/list → tools/call
[03]

Isolated secrets

ERP credentials are encrypted per tenant. They never reach the agent.

AES-GCM · DEK per tenant
[04]

Outbound tunnel

When the ERP isn't reachable, a small bridge process at the customer opens an outbound connection. No public exposure.

direct | tunnel

// Audit trail

Explicit execution contract.

Every call keeps its tenant, target ERP, connection mode and result. Readable in support, actionable in audit.

[tenant]   acme.erp-platform.fr
[stack]    @casys/mcp-server · mcp-bridge · mcp-compose
[erp]      @casys/mcp-erp adapter contract
[erpnext]  depth proven → mcp-erpnext
[dolibarr] adapter contract · progressive mapping
[einvoice] mcp-einvoice extension
[auth]     session tenant matched
[runtime]  direct | tunnel (pilot)

07 — Programme pilote

An ERP to connect?
Scope defined together, before any access.

ERP in use, data to expose, network constraints. You describe the case. We come back with a concrete trial plan.

Technical question

✕ No ERP credential is requested in the form.