Skip to main content
Glama
GutjahrAI

SAP OData MCP Server

by GutjahrAI

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
SAP_CLIENTNoOptional SAP client number (e.g., 100)100
SAP_TIMEOUTNoOptional request timeout in milliseconds (default: 30000)30000
SAP_PASSWORDYesThe SAP password for authentication
SAP_USERNAMEYesThe SAP username for authentication
SAP_ENABLE_CSRFNoWhether to enable automatic CSRF token management.true
SAP_VALIDATE_SSLNoWhether to validate SSL certificates. Set to 'false' for development with self-signed certificates.false
SAP_ODATA_BASE_URLYesThe base URL for SAP OData services (e.g., https://your-sap-host:8000/sap/opu/odata/sap/)

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

CapabilityDetails
tools
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
sap_connectC

Connect to SAP OData service

sap_get_servicesB

Get list of available OData services

sap_get_service_metadataC

Get metadata for a specific OData service

sap_query_entity_setC

Query an OData entity set with filtering, sorting, and pagination

sap_get_entityC

Get a specific entity by its key values

sap_create_entityC

Create a new entity in an entity set

sap_update_entityC

Update an existing entity

sap_delete_entityC

Delete an entity

sap_call_functionC

Call an OData function import

sap_connection_statusB

Check SAP OData connection status and get connection info

sap_disconnectA

Disconnect from SAP OData service

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

TDQS

A3.5/5.0

Scored across 11 tools

Disambiguation5/5

Every tool has a clearly distinct purpose with no ambiguity. Each tool targets a specific OData operation (e.g., connect, query, create, update, delete) or metadata retrieval, making it easy for an agent to select the right tool without confusion.

Naming Consistency5/5

Tool names follow a consistent 'sap_verb_noun' pattern throughout, using snake_case uniformly. This predictable naming scheme enhances readability and makes the tool set easy to navigate and understand.

Tool Count5/5

With 11 tools, the server is well-scoped for SAP OData operations. Each tool earns its place by covering essential CRUD operations, connection management, and metadata retrieval, providing a comprehensive yet manageable surface for the domain.

Completeness5/5

The tool set offers complete CRUD/lifecycle coverage for SAP OData, including connection handling, entity management, and metadata access. There are no obvious gaps, ensuring agents can perform all core workflows without dead ends.

Maintenance

ActivityInactive
ResponsivenessNo issues