Skip to main content
Glama
onec-odata-mcp

onec-odata-mcp

by pyrfor

Related Servers

Alternatives to onec-odata-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables 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.
      8
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Give 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.
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables ChatGPT's desktop Codex app to query a live 1C (1С) database through OData in read-only mode, so users can ask plain-language questions about sales, stock, items, and counterparties, and get answers, charts, and dashboards without exports or programming.
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables 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
      ISC
    • A
      license
      Not graded
      quality
      A
      maintenance
      Integrates 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.
      337
      GPL 3.0

    TDQS

    A3.7/5.0

    Scored across 8 tools

    Disambiguation5/5

    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.

    Naming Consistency3/5

    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).

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues