onec-odata-mcp
Related Servers
Alternatives to onec-odata-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables users to ask natural-language questions about live 1C:Enterprise data and receive answers from read-only OData sources, covering sales, inventory, items, and counterparties; supports direct connections or an SSH tunnel for IP-allowlisted installations.1MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to interact with 1C:Enterprise databases through natural language, providing metadata retrieval, configuration analysis, and code generation.9-
- FlicenseNot gradedqualityDmaintenanceGive an AI agent eyes into your 1C:Enterprise 8.3 base — read metadata & data, run queries, and diagnose why a document won't post — over one extension HTTP service.-
- FlicenseAqualityDmaintenanceEnables AI agents to interact with 1С:Enterprise and BAS ERP systems through REST and HTTP services, providing tools for searching catalogs, creating documents, and querying stock balances.6-
- AlicenseNot gradedqualityBmaintenanceIntegrates AI agents with 1C:Enterprise databases via MCP and REST API, supporting a built-in HTTP server (no Python required) or a Python proxy mode.304GPL 3.0
- FlicenseNot gradedqualityFmaintenanceEnables Claude to interact with 1C:Enterprise via OData REST API, allowing natural language queries for inventory, orders, prices, and order creation.-
TDQS
Scored across 8 tools
All eight tools have clearly distinct purposes: building query parameters, counting records, explaining entity fields, summarizing financial entities, listing entities, retrieving metadata, checking configuration, and executing queries. There is no overlap or ambiguity between tools.
All tools use the consistent 'odata_' prefix in snake_case, but the second part mixes verbs (build, count, explain, list, query) and nouns (config, financial_summary, metadata). A fully consistent pattern would use verbs consistently (e.g., odata_get_config, odata_get_metadata).
With 8 tools, the set is well-scoped for interacting with 1C OData services. It covers listing, querying, metadata retrieval, configuration check, and specialized financial summarization without being bloated or too sparse.
The set covers core read operations (list, query, count, metadata, config) and adds a specialized financial summary. Missing are create/update/delete operations, but these may be out of scope. A minor gap is the lack of a direct 'get entity by ID' tool, though query with filter can achieve this.