io.github.Coaspe/sap-abap-mcp
SAP ABAP MCP
Develop, test, analyze, and operate SAP ABAP systems through ADT from AI coding agents.
alive probed 2026-10-19
5tools
≈ 578tokens, estimate
≈ 0.3 %of Claude's 200k window
0.4×the median server
1.5 sto initialize
6 msto list tools
- Run it
- npx -y @coaspe/sap-abap-mcp@2.0.1 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Reports itself as
- sap-abap-mcp 2.0.1
- Capabilities
- completions, prompts, resources, tools
- Instructions
- 397 characters
- Of a 1M window
- ≈ <0.1 % of a 1M context window, estimate
- Claude count
- The count_tokens endpoint refused the tool schemas: invalid x-api-key. The estimate stands in.
- Repository
- https://github.com/Coaspe/sap-abap-mcp
- Website
- https://github.com/Coaspe/sap-abap-mcp
- Registry
- active, updated 2026-10-12 · registry entry
- Reachable
- 1 of the last 1 probe
Most expensive tools
Estimates with the o200k_base tokenizer.
| Tool | o200k estimate | Share of this server |
|---|---|---|
| sap.capability.search | 127 | 22 % |
| sap.capability.invoke_destructive | 115 | 20 % |
| sap.capability.invoke_read | 114 | 20 % |
| sap.capability.invoke_write | 114 | 20 % |
| sap.capability.describe | 108 | 19 % |
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The Anthropic count_tokens endpoint refused the tool schemas (invalid x-api-key). A client that validates schemas can refuse them too.