sap-odata-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SAP_API_KEY | Yes | Your SAP API key from api.sap.com, used to authenticate against the SAP S/4HANA Cloud sandbox. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| sap_list_servicesA | List the SAP S/4HANA OData services this server can query, with descriptions and key entity sets. Call this first. |
| sap_describe_entity_setA | Return the fields (name, type, label), keys and navigation properties of an entity set, from the service $metadata. Call this before building a $filter or $select so you use real field names. |
| sap_queryA | Read records from an SAP OData V2 entity set using OData query options. Filter syntax examples: "SalesOrderType eq 'OR'", "TotalNetAmount gt 1000", "substringof('Inc', BusinessPartnerName)". Dates: "CreationDate ge datetime'2024-01-01T00:00:00'". |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.