ONE-MCP
Related Servers
Alternatives to ONE-MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceA remote MCP server that connects Claude to Acumatica ERP, enabling per-user OAuth-authenticated access to over 40 tools for querying and managing Acumatica data with role-based security and sensitive field redaction.Apache 2.0
- FlicenseAqualityDmaintenanceAn advanced MCP server that enables Claude Desktop to act as an autonomous Oracle Database Administrator and Data Analyst with agentic schema discovery and self-healing queries.21-
- AlicenseNot gradedqualityAmaintenanceAn MCP server that enables AI assistants like Claude to interact with Odoo ERP systems through natural language, allowing users to search, create, update, and manage business data in their Odoo instance.1,571 PyPI384Mozilla Public 2.0
- FlicenseNot gradedqualityBmaintenanceMCP server that integrates Claude with the Omie ERP, enabling query and execution of operations across all Omie modules (e.g., production orders, inventory, purchases, CRM, finance, sales, services) via natural language MCP tools.8 npm-
- FlicenseNot gradedqualityDmaintenanceMCP server that integrates with Microsoft Dynamics 365 Business Central, enabling querying of customers, items, and sales orders through natural language commands in Claude Desktop.10-
- -licenseNot gradedqualityCmaintenanceA remote MCP server that lets Claude securely interact with an Acumatica ERP instance using per-user OAuth, role-based access control, and automatic redaction of sensitive fields.-
TDQS
Scored across 10 tools
Each tool targets a distinct action and resource: instance info, querying, entity metadata, entity records, and workflows. Even overlapping tools like fetch_query and get_entity_record are clearly differentiated by purpose (discovery vs. direct lookup).
Most tools follow a verb_noun pattern (get_, list_, create_, update_, execute_), but 'fetch_query' deviates from the get_/list_ convention. Entity-specific tools share a consistent 'get_entity_*' prefix, and workflow tools follow 'list/get/execute_workflow'.
With 10 tools, the set is well-scoped for the server's purpose: exploring the data model, querying data, managing entities, and executing workflows. No tool feels redundant, and the count supports a complete workflow without being bloated.
The tool surface covers metadata discovery, querying, record creation/update, and workflow execution. The explicit lack of delete functionality is a notable gap, but it is acknowledged and likely intentional for safety. Read and update paths are fully covered, so agents can accomplish most tasks.