Introduction
ERPBridge connects existing ERP APIs to AI agents through the Model Context Protocol (MCP).
It exposes ERP functionality as MCP tools, so agents like Claude, Cursor, and other MCP-compatible clients can discover and call ERP operations without writing custom integrations.
See the Agentic Tools MCP Integration guide for Codex CLI, OpenCode, OpenClaw, and Hermes Agent setup.
Why ERPBridge?
- Standards-based — implements MCP over Streamable HTTP and stdio.
- Tool registry — register ERP APIs once, generate and validate MCP tool schemas.
- Resilient — provides caching, rate limiting, and connection handling for upstream ERP systems.
- Observable — structured JSON logs, Prometheus metrics, and a health endpoint.
- Agent-friendly — provides the
bridgectlCLI for local development and CI workflows.
Components
| Component | Description |
|---|---|
erpbridge-server | The ERPBridge Server middleware (HTTP + stdio transports). |
bridgectl | Developer CLI to register APIs, manage tools, and monitor the middleware. |
mock-erp | A mock ERP service (FastAPI) for local development and testing. |
@erpbridge/sdk | TypeScript client library — MCP tools, REST invocation, logs, metrics, health, and cache (SDK docs). |
Choose a documentation path
This site organizes the documentation by component:
- Server — everything about
erpbridge-server: quickstart, transports, REST API. bridgectl— the complete CLI reference: overview and every command.- ERPBridge SDK — everything about
@erpbridge/sdk: overview, quickstart, MCP tools, logs and metrics.
Getting started
Start with the quickstart. If you already run ERPBridge Server, read the Connectivity and transport guide.