mcp-erp-bridge
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@mcp-erp-bridge look up work order 12345678 and show me its status"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
mcp-erp-bridge
A Model Context Protocol server that wraps a session-cookie-authenticated enterprise web app (an ERP, a work-order system, a ticketing portal) and exposes structured tools to any MCP-compatible client.
This is a reference implementation of a deployment pattern: turning an internal-only enterprise web app with no API into an MCP server so non-technical operators can drive it with Claude Code, Claude Desktop, or any other MCP client.
The pattern is deliberately generic. Endpoint paths, login form fields, the
session cookie name, and every HTML selector live in one config object
(ErpConfig) and can be overridden from a JSON file, so the same code
adapts to any system with a cookie-based auth flow and HTML pages.
Why this exists
Most MCP examples wrap clean SaaS APIs (Slack, Linear, GitHub). The real deployment surface in the messy middle of the economy is internal enterprise tools with no public API and a session cookie for auth. This server is a worked example of how to wrap one.
The shape: a server, a handful of tools, a typed schema on every call, and an opinionated deterministic-core / probabilistic-edge split.
Related MCP server: HyperCrawl
Tool status
Tool | Status |
| Implemented |
| Implemented |
| Implemented |
| Designed (schema + overtime walk-back logic ready; schedule-export parser not bundled) |
| Designed (schema ready; awaits roster iteration on a real backend) |
Three tools are fully wired against the HTTP client. The two scheduling
tools have schemas and supporting logic in schemas.py and overtime.py,
but the schedule-export parser is intentionally not bundled: every system
serves schedules differently, and shipping a stub would be dishonest.
Features
Three production-ready tools plus two designed-but-unbundled
Session-cookie + CSRF auth with automatic refresh on 401
SQLite cookie cache so re-auth happens once per session window, not per call
Selector-driven parsing: every CSS selector, form field, and endpoint path is configuration, not code
Pydantic schemas on every tool input/output: Claude sees a typed contract, not a free-form dict
Stdio transport for Claude Code / Claude Desktop integration
Injectable HTTP transport so the whole client is testable offline
MIT licensed: fork it, point it at your own system
Install
From source:
git clone https://github.com/mffnxman/mcp-erp-bridge
cd mcp-erp-bridge
pip install -e ".[dev]"Configure
Credentials come from the environment:
export ERP_USERNAME="your.login@example.com"
export ERP_PASSWORD="..."
export ERP_BASE_URL="https://erp.example.com"Endpoints and selectors come from an optional JSON file. Copy
examples/erp_config.example.json, edit it to match your system's markup,
and point at it:
export ERP_CONFIG_FILE="/path/to/erp_config.json"Any key you leave out keeps its default. Unknown keys raise at startup so typos don't silently fall back to placeholders.
{
"endpoints": { "login": "/account/signin", "work_order": "/orders/{wo_number}" },
"selectors": {
"session_cookie": "ASPSESSIONID",
"detail_fields": { "status": "span.order-state", "technician": "#assigned-to" },
"list_rows": "table#orders tr.row"
}
}Use with Claude Desktop
Add to ~/Library/Application Support/Claude/claude_desktop_config.json
(or the Windows equivalent at %APPDATA%\Claude\claude_desktop_config.json):
{
"mcpServers": {
"erp-bridge": {
"command": "python",
"args": ["-m", "mcp_erp_bridge"],
"env": {
"ERP_USERNAME": "your.login@example.com",
"ERP_PASSWORD": "...",
"ERP_BASE_URL": "https://erp.example.com",
"ERP_CONFIG_FILE": "/path/to/erp_config.json"
}
}
}
}Use with Claude Code
claude mcp add erp-bridge python -m mcp_erp_bridge \
-e ERP_USERNAME=your.login@example.com \
-e ERP_PASSWORD=... \
-e ERP_BASE_URL=https://erp.example.com \
-e ERP_CONFIG_FILE=/path/to/erp_config.jsonTools
get_work_order(wo_number: str) -> WorkOrder
Fetches a single work order by number. Returns the full structured record: status, assigned technician, schedule, NTE, customer, location, parent work order, and the close-out fields.
get_work_order("12345678")
-> WorkOrder(
number="12345678",
status="In Progress",
technician="Doe, Jane",
scheduled="2026-05-08 14:00",
nte=850.00,
closeout_fields={...}
)list_pending_work(manager: str = None) -> List[WorkOrder]
Returns all work orders currently pending dispatch or in progress, optionally filtered to a single manager.
list_pending_work(manager="Doe, Jane")
-> [WorkOrder(...), WorkOrder(...), ...]add_closeout_note(wo_number: str, fields: CloseoutFields) -> NoteResult
Adds a close-out note to a work order with all required fields templated from structured input. Validates every field before submission; raises rather than silently submitting an incomplete note.
Architecture
+-----------------+ stdio +-----------------+
| MCP Client |<--------->| mcp-erp-bridge |
| (Claude Code) | | server |
+-----------------+ +--------+--------+
| tool calls
+--------v--------+
| ErpClient |
| (httpx + SQLite |
| cookie cache) |
+--------+--------+
| HTTPS
v
+-----------------+
| Enterprise ERP |
| (session cookie |
| + CSRF) |
+-----------------+The deliberate choice: all "right-answer" logic is deterministic Python. Claude is only on the probabilistic edge: drafting prose, summarizing, matching intent. Tool calls go straight to deterministic Python. This is the pattern that survives production.
Project structure
mcp-erp-bridge/
+-- README.md
+-- LICENSE
+-- pyproject.toml
+-- src/
| +-- mcp_erp_bridge/
| +-- __init__.py
| +-- __main__.py
| +-- server.py # MCP server + tool registration
| +-- erp_client.py # HTTP client w/ cookie cache
| +-- config.py # endpoints, selectors, credentials
| +-- schemas.py # Pydantic models
| +-- overtime.py # overtime walk-back recovery logic
+-- examples/
| +-- claude_desktop_config.json
| +-- erp_config.example.json
| +-- usage.md
+-- tests/
+-- test_client.py # login, cookie cache, 401 re-auth, parsing (mocked HTTP)
+-- test_schemas.py # input validation
+-- test_overtime.py # walk-back logicTests
python -m pytest -qThe client tests run against httpx.MockTransport; no network, no real
system.
Background
This is a reference implementation, not a product. The shape (a session-cookie login, a CSRF token, HTML pages instead of an API, a handful of typed tools with a deterministic core and a probabilistic edge) is the shape of most internal enterprise tools, so anyone wrapping one can fork this and swap the selectors. Every URL, field name, cookie name, and selector is a configurable placeholder; none of them point at a real system.
License
MIT (c) 2026 Rafael Garcia
Available Tools
3 toolsadd_closeout_noteB
Submit a close-out note with all required fields. Validates every field; raises rather than submitting incomplete.
Inputs: fields (required), wo_number (required).
get_work_orderA
Look up a single work order by its number. Returns full structured record: status, technician, schedule, NTE, customer, location, parent WO, and the close-out fields.
Inputs: wo_number (required).
list_pending_workB
List all pending-dispatch and in-progress work orders, optionally filtered to a single manager.
Inputs: manager, include_in_progress.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 3 tools
Each tool targets a distinct action and resource: get_work_order retrieves a single record, list_pending_work lists multiple records, and add_closeout_note submits a note. There is no overlap in purpose, making selection unambiguous.
All tool names follow a consistent verb_noun pattern in snake_case: get_work_order, list_pending_work, add_closeout_note. The verbs (get, list, add) clearly indicate the action, and the nouns are descriptive.
Three tools is on the low end for an ERP bridge, but they form a coherent subset for a specific work order closeout workflow. It is slightly under what might be expected for broader ERP work order management, but not unreasonable.
The set covers read (single and list) and one write (closeout note), but lacks create, update, delete, and broader listing operations for work orders. These gaps would cause failures for agents needing to manage the full work order lifecycle.
Maintenance
Related MCP Connectors
ServiceTrade MCP server for ChatGPT, Claude and any AI agent: list jobs, create appointment, release appointment to technicians, list deficiencies, create quote, submit quote and add comment to job in your own ServiceTrade account. Cotlet works in the account through your Cloud Browser, a real Chrome where you sign in to ServiceTrade yourself; Cotlet does not store your password and you need no ServiceTrade API key. About the official ServiceTrade API: ServiceTrade has a full REST API with public docs and OAuth2 client-credentials sign-in, but no official MCP server (checked 23 Oct 2026). The API covers jobs, appointments, deficiencies and quotes, so the missing piece is the agent layer: you build and host the wrapper yourself. Setup and FAQ: https://cotlet.dev/integrations/servicetrade-api-mcp-server
Autonomous Website Intelligence & OSINT Suite for AI Agents (10 Tools) Surgically extract clean token-optimized Markdown for RAG, detect 65+ tech stacks, identify corporate mail providers (Google Workspace vs Microsoft 365), and audit SSL/security posture with hardened SSRF protection. Quick Install in Claude Desktop (claude_desktop_config.json): json { "mcpServers": { "webintel": { "command": "npx", "args": ["-y", "@modelcontextprotocol/server-fetch", "https://webintel-apis.vercel.app/api/mcp"] } } }
Run field service from Claude, ChatGPT or Copilot: dispatch, billing, customer messages, photos, and change the software itself, with a confirm step before every change. This address is the India region; US East, Canada, Norway and NZ addresses are at fieldproxy.ai/mcp.
FieldEdge MCP server for ChatGPT, Claude and any AI agent: create work order, dispatch technician, list customers, send invoice and list unpaid invoices in your own FieldEdge account. Cotlet works in the account through your Cloud Browser, a real Chrome where you sign in to FieldEdge yourself; Cotlet does not store your password and you need no FieldEdge API key. About the official FieldEdge API: FieldEdge has an API, but only on request: customers ask for access through FieldEdge's onboarding form and get credentials for an app FieldEdge provisions (checked 8 Nov 2026). There are no self-service keys and no official MCP server. Setup and FAQ: https://cotlet.dev/integrations/fieldedge-api-mcp-server
Related MCP Servers
- AlicenseAqualityBmaintenanceA Model Context Protocol (MCP) integration that provides Claude Desktop with autonomous browser automation capabilities. This agent enables Claude to interact with web content, manipulate DOM elements, execute JavaScript, and perform API requests.1343TypeScriptMozilla Public 2.0
- FlicenseNot gradedqualityDmaintenanceSelf-hosted, cookie-aware web-automation engine that turns any website into callable MCP tools, with stateful browser sessions, web search, and multi-page crawling.-
- -licenseNot gradedqualityCmaintenanceEnables AI agents to discover and call business actions from browser-only legacy web applications as typed MCP tools, executing them through the original GUI via Playwright.-
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients like Claude to enter and query expenses, invoices, and contracts in a WorkPulse instance via its REST API, with 14 tools, batch rollback, and stdio or OAuth-protected Streamable HTTP transports while keeping credentials server-side.MIT