Guided pilots · ERPNext as the reference

mcp-erpnext · MCP

Your ERP in Claude and ChatGPT—under control.

Casys scopes the actions, builds the remote MCP server and hosts it around one concrete workflow. ERPNext is our public reference; every hosted service remains a guided pilot, not an open self-service catalog.

View mcp-erpnext on GitHub
Open-source proof
mcp-erpnext
124 tools · 7 Apps
Managed pilot
Hosted MCP
OAuth · tenant · isolation
Discovery first
Another business system
API assessed first

MCP clients

One remote endpoint for Claude, supported ChatGPT workspaces and the other MCP clients your team chooses.

Starting points

Already have an ERP—or start with ERPNext.

Either way, we begin with a workflow and a list of expected actions, never unrestricted access to your system.

Three ways to start

Your existing ERP

ERPNext first

Keep your system. We assess its API and workflow, build the dedicated integration, then host the MCP endpoint. ERPNext comes first; other ERPs are assessed before we commit.

Managed ERPNext + MCP

Quoted pilot

For a new pilot, we can scope a dedicated ERPNext instance, initial configuration, MCP access, backups and operations.

Another business system

Discovery first

CRM, invoicing, support or an internal application: we assess the API and workflow before committing. No universal connector is promised.

Scope

01

An explicit workflow, not total access.

The expected data and actions are defined before the MCP is built or opened.

Identity

02

OAuth/OIDC in front of the endpoint.

The client authenticates before runtime. In direct mode, ERP credentials are encrypted on the platform; in tunnel mode, they remain in the local agent.

Network

03

Direct API or an assessed tunnel.

The pilot's business surface requires a dedicated API integration; an outbound tunnel is assessed for a private ERP.

Operations

04

Hosting, call traces and support.

Once the surface is integrated, successful calls emit best-effort tenant events for support and incident review.

Pilot method

A useful pilot starts with one precise action.

Look up a customer, prepare a quote, follow up on an invoice: we start with a verifiable business outcome and expose only the surface it needs.

  1. Step 01

    Choose the workflow

    We describe what the agent must read, prepare or execute in one real use case.

    workflow.scope → explicit
  2. Step 02

    Set the boundaries

    Data, actions, users and authority limits are made explicit before integration.

    authority.define → approved
  3. Step 03

    Connect the system

    During the pilot, we build the direct API integration or assess an outbound tunnel when the system must stay private.

    mcp.integrate → direct | tunnel
  4. Step 04

    Validate in the client

    The path is tested in the chosen MCP client before the pilot is opened to the team.

    client.verify → ready

Guided pilots · ERPNext as the reference

Need an MCP for your ERP—or another business system?

Tell us what the agent should read, prepare or execute, in which system and under which constraints. We will return with a pilot scope—or tell you plainly if MCP is not the right fit.

We start with a verifiable workflow, not a catalog of tools.

The form never asks for ERP credentials. Client and plan compatibility are checked during scoping.