sap-odata-mcp
Related Servers
Alternatives to sap-odata-mcp
No user-submitted related servers found.
Related Servers
- FlicenseAqualityDmaintenanceEnables interaction with SAP S/4HANA systems via OData, allowing service discovery, metadata exploration, field value retrieval, and CRUD operations through natural language.45-
- AlicenseAqualityDmaintenanceEnables AI assistants to integrate with SAP systems via OData REST APIs for querying entity sets, performing CRUD operations, and executing function imports. It features automatic service discovery, CSRF token management, and smart connection handling without requiring the SAP RFC SDK.1113MIT
- AlicenseNot gradedqualityCmaintenanceEnables Claude, ChatGPT, Copilot and Cursor to explore and query SAP S/4HANA's HANA database using SAP's data dictionary, organization structure, CDS views, and read-only SQL, with tools for finding tables, fields, joins, code values, and running SELECT queries. All access is read-only, with encrypted credentials and audited calls.2AGPL 3.0
- AlicenseNot gradedqualityCmaintenanceEnables natural-language querying and authenticated CRUD operations against SAP S/4HANA or ECC OData services through dynamic MCP tools with progressive service and entity discovery.54 npmMIT
- AlicenseNot gradedqualityNot gradedmaintenanceTurns any OData V2 or V4 service, SAP Gateway included, into MCP tools that AI clients such as Claude, ChatGPT, Copilot, and Cursor can call without code by reading $metadata. It lets models discover entity sets and fields, then query services through built-in read-only tools.AGPL 3.0
- FlicenseBqualityCmaintenanceEnables AI assistants to explore and query SAP BW/4HANA modeling objects and metadata, such as InfoAreas, InfoObjects, ADSOs, CompositeProviders, and Queries.15-
TDQS
Scored across 3 tools
Each tool targets a distinct step in a clear workflow: discover services, inspect an entity set's schema, then query records. Descriptions even state ordering guidance ('call this first', 'call this before building a $filter'), leaving no realistic chance of misselection.
All three tools use a uniform sap_ prefix followed by a snake_case verb_noun form (list_services, describe_entity_set, query). The pattern is predictable and self-documenting.
Three tools is on the thin edge but each has a clear, non-redundant role for a read-only OData gateway. It is well-scoped rather than padded, though the surface is minimal enough that some agents may want more entry points.
Discovery, schema introspection and querying are covered, but the surface is read-only: no create/update/delete, no function imports or actions, no count or paging helpers. These gaps are defensible for a query-focused server but will block write workflows.