Business operationsPublic source

ERP MCP Server

The most complete multi-backend ERP MCP server. 44 tools across 6 backends — SAP S/4HANA, NetSuite, Odoo, Zoho Books, Microsoft Dynamics 365 Business Central, and Zavora ERA. Lifecycle-based document management with…

Open the source Read the official guide ↗

What it gives an agent

A purpose-built capability behind one MCP connection.

The server owns its domain logic and publishes a tool contract an MCP client can discover. ADK-Rust can load that contract into an agent, normalize each schema for the chosen model provider, and keep the connection lifecycle outside the agent’s business logic.

Unified schema — agents see consistent types (Customer, Vendor, Product, SalesOrder, Invoice) regardless of backend

Lifecycle-based writes — documents progress through states (draft → pending_approval → approved → released → posted → closed) instead of single-step creates

Feature-flagged backends — compile only what you need (--features zoho,odoo,sap)

Financial governance — invoice posting and order submission require approval gates

No credential exposure — tokens stay in env vars, never reach LLM context

Single binary — no Node.js, no Python, no runtime dependencies

Architecture

How ERP MCP Server fits into an agent system.

The model never needs the implementation details or credentials of the system behind the server. It sees reviewed tool definitions. The MCP client handles discovery and calls, while the server keeps ownership of validation, policy, and communication with its domain system.

ADK-Rust agent

Chooses a capability from the reviewed tool catalog.

→

MCP client

Discovers schemas, sends calls, and receives typed content.

→

ERP MCP Server

Validates the request and owns 44 documented tool contracts.

→

Domain system

Keeps the API, data, credentials, and business rules behind the server.

Connection: stdio · Server framework: ADK MCP SDK + rmcp

ERP MCP Server architecture diagram from its official repository

Tool catalog

What can an agent ask ERP MCP Server to do?

Each tool has a stable name, a human-readable purpose, and a JSON input contract discovered during MCP initialization. Risk classes come from the project’s registry manifest when one is available.

34 named tools shown from 44 documented tools

list_customers

List customers with optional filters

read only

get_customer

Get a customer by ID

read only

create_customer

Create a new customer record

internal write

update_customer

Update an existing customer record

internal write

list_vendors

List vendors/suppliers with optional filters

read only

get_vendor

Get a vendor by ID

read only

create_vendor

Create a new vendor/supplier record

internal write

update_vendor

Update an existing vendor record

internal write

list_products

List products/items with optional filters

read only

get_product

Get a product by ID

read only

create_product

Create a new product/item record

internal write

update_product

Update an existing product record

internal write

Governance

Understand the effect of every tool.

A server connection inherits the authority of its credentials and deployment environment. The declarations below come from this project’s README and MCP registry manifest; your application still decides which tools an agent receives and where approval is required.

17 read only13 internal write2 external write2 financial action

Lifecycle-based writes — documents progress through states (draft → pending_approval → approved → released → posted → closed) instead of single-step creates
Financial governance — invoice posting and order submission require approval gates

MCP surface

What the current documentation declares.

MCP can carry tools, resources, prompts, structured results, progress, cancellation, and long-running work. This record highlights the modern protocol features explicitly mentioned by this repository.

The current README concentrates on its tool surface. Check the source and release notes before relying on optional MCP capabilities beyond tool discovery and invocation.

ADK MCP SDKrmcpRegistry manifest

Install and connect

Follow the project’s documented starting point.

Install the server in the environment that owns its credentials and domain access. Add it to your MCP host, verify the discovered tools, and narrow the toolset before giving it to a production agent.

Install

cargo install mcp-erp --features all-backends

MCP client configuration

export ZAVORA_API_URL="http://localhost:8080"
export ZAVORA_EMAIL="agent@company.co.ke"     # service user
export ZAVORA_PASSWORD="secret"               # JWT login; token auto-refreshes

Commands and configuration are extracted from the public README. Confirm prerequisites, environment variables, and release-specific options in the official documentation before deployment.

Official documentation

Continue with the project maintainers’ source of truth.

This page provides an approachable map of the server. The repository remains authoritative for exact schemas, prerequisites, configuration, examples, tests, releases, and security updates.

Overview ↗README.md CHANGELOG ↗CHANGELOG.md Api Reference ↗docs/api-reference.md Architecture ↗docs/assets/architecture.svg Issues and support ↗github.com issues

Keep exploring