mcp-erp-bridge
Related Servers
Alternatives to mcp-erp-bridge
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceTurns YAML-defined browser flows into typed MCP tools that Claude, Cursor, VS Code and other MCP clients can call, letting agents run repeatable tasks like logins, form fills, report downloads, price checks and data extraction without letting them wander the page freely. Each call returns JSON output, downloaded files or screenshots, and failures report the step, error, page URL and a screenshot.0MIT
- 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
- AlicenseNot gradedqualityAmaintenanceConnects MCP-compatible AI agents to an anti-detection browser server, exposing dozens of tools for navigation, page interaction, search, content extraction, downloads, multi-tab handling, and persistent sessions. It lets agents automate and scrape the web at scale using accessibility snapshots, CSS-selector fallbacks, saved profiles, and batch workflows over stdio or authenticated HTTP transport.971 npmMIT
- FlicenseNot gradedqualityCmaintenanceSelf-hosted, cookie-aware web-automation engine that turns any website into callable MCP tools, with stateful browser sessions, web search, and multi-page crawling.-
- AlicenseAqualityAmaintenanceA 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.1310 npm43TypeScriptMozilla Public 2.0
- -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.-
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.