Skip to main content
Glama

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
MCP_PORTNoPort for Streamable HTTP server (configurable via MCP_PORT)3122

Tools

Functions exposed to the LLM to take actions

NameDescription
sap_community_search

SEARCH SAP COMMUNITY: sap_community_search(query="search terms")

FUNCTION NAME: sap_community_search (or mcp_sap-docs-remote_sap_community_search)

FINDS: Blog posts, discussions, solutions from SAP Community INCLUDES: Engagement data (kudos), ranked by "Best Match"

TYPICAL WORKFLOW:

  1. sap_community_search(query="your problem + error code")

  2. fetch(id="community-12345") for full posts

BEST FOR TROUBLESHOOTING: • Include error codes: "415 error", "500 error" • Be specific: "CAP action binary upload 415" • Use real scenarios: "wizard implementation issues"

sap_help_search

SEARCH SAP HELP PORTAL: sap_help_search(query="product + topic")

FUNCTION NAME: sap_help_search (or mcp_sap-docs-remote_sap_help_search)

SEARCHES: Official SAP Help Portal (help.sap.com) COVERS: Product guides, implementation guides, technical documentation

TYPICAL WORKFLOW:

  1. sap_help_search(query="product name + configuration topic")

  2. sap_help_get(result_id="sap-help-12345abc")

BEST PRACTICES: • Include product names: "S/4HANA", "BTP", "Fiori" • Add specific tasks: "configuration", "setup", "deployment" • Use official SAP terminology

sap_help_get

GET SAP HELP PAGE: sap_help_get(result_id="sap-help-12345abc")

FUNCTION NAME: sap_help_get (or mcp_sap-docs-remote_sap_help_get)

RETRIEVES: Complete SAP Help Portal page content REQUIRES: Exact result_id from sap_help_search

USAGE PATTERN:

  1. Get ID from sap_help_search results

  2. Use exact ID (don't modify the format)

  3. Receive full page content + metadata

search

SEARCH SAP DOCS: search(query="search terms")

FUNCTION NAME: search

COVERS: ABAP (all versions), UI5, CAP, wdi5, OpenUI5 APIs, Cloud SDK AUTO-DETECTS: ABAP versions from query (e.g. "LOOP 7.57", defaults to 7.58)

TYPICAL WORKFLOW:

  1. search(query="your search terms")

  2. fetch(id="result_id_from_step_1")

QUERY TIPS: • Be specific: "CAP action binary parameter" not just "CAP" • Include error codes: "415 error CAP action" • Use technical terms: "LargeBinary MediaType XMLHttpRequest" • For ABAP: Include version like "7.58" or "latest"

fetch

GET SPECIFIC DOCS: fetch(id="result_id")

FUNCTION NAME: fetch

RETRIEVES: Full content from search results WORKS WITH: Document IDs returned by search

ChatGPT COMPATIBLE: • Uses "id" parameter (required by ChatGPT) • Returns structured JSON content • Includes full document text and metadata

Prompts

Interactive templates invoked by user choice

NameDescription
sap_search_helpHelps users construct effective search queries for SAP documentation
sap_troubleshootGuides users through troubleshooting common SAP development issues

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/marianfoo/mcp-sap-docs'

If you have feedback or need assistance with the MCP directory API, please join our Discord server