SAP MCP Server

SAP MCP Quick Context

sap_quick_context

Read-onlyIdempotent

Free single-call bootstrap aggregator. Returns a compact markdown-like summary with server version, total tools count, tools by category, pricing tiers summary, premium plugins/capabilities count, bundled skills list, and nextAction guidance. Pass agentKnownVersion with the version you currently know to get skillsUpdateRequired + skillsContents (full SKILL.md inline) when the server version differs — this lets you auto-update your local skills in 1 call without a separate sap_skills_bundle. Use this instead of calling sap_agent_start, sap_pricing_catalog, sap_premium_plugin_catalog, sap_skills_list, and sap_get_tool_category_summary separately to reduce bootstrap from 5+ tool calls to 1.

SAP MCP execution guidance: Intent: SAP MCP tool workflow. Pricing: free; call directly without x402. Routing: free hosted call; call directly and keep it small/exact when possible. Signer boundary: hosted reads/builders never receive keypair bytes; value-moving results must be finalized locally when signing is required.

Input Schema

TableJSON Schema

Name	Required	Description
`intent`	No	Optional user intent for the embedded sessionContextPacket. Use this to route bootstrap toward paid calls, registry writes, swaps, escrow, external x402 agents, premium streams, balance reads, or discovery.
`compact`	No	When true (default), the summary string is kept compact. When false, a more readable multi-line summary is returned.
`include`	No	Optional subset of section names to include (version, tools, pricing, premium, skills, nextAction). When omitted, all sections are returned.
`maxChars`	No	Maximum character length for the summary string. Defaults to 4000. The summary is truncated if it exceeds this length.
`agentKnownVersion`	No	The SAP MCP version the agent currently knows about. When this differs from the server version, skillsUpdateRequired is set to true and skillsContents is populated with full SKILL.md contents. Omit to always force a skills update (first bootstrap).

Output Schema

TableJSON Schema

Name	Required	Description
`skills`	Yes	Bundled skill names available via sap_skills_bundle.
`success`	Yes	Whether the quick context summary was generated.
`summary`	Yes	Compact markdown-like summary string suitable for agent context loading.
`version`	Yes	SAP MCP server version.
`truncated`	Yes	Whether the summary was truncated to fit within maxChars.
`nextAction`	Yes	Concrete next action for the agent after loading this context.
`totalTools`	Yes	Total number of registered MCP tools.
`environment`	Yes	Server environment summary: network (mainnet/devnet), mode (hosted-api/local-dev-keypair/readonly), authType (none/bearer), rateLimitPerMinute.
`toolCatalog`	Yes	Secret-free modular tool catalog summary with selected modules, payment tiers, signer-boundary policy buckets, and hosted/local bridge hints.
`pricingTiers`	Yes	Pricing tier names available on the hosted server.
`serverCommit`	Yes	Git commit hash of the running server build. Changes on every deploy even without version bump.
`premiumPlugins`	Yes	Number of discoverable premium plugins.
`skillsContents`	No	Full SKILL.md contents of all bundled skills, included only when skillsUpdateRequired is true. Each entry has {name, content}.
`recommendedFlow`	Yes	Recommended agent workflow based on server mode. Hosted: build unsigned → sign locally. Local: preview → sign → submit.
`toolsByCategory`	Yes	Tool counts by category (sap, sns, agentKit, premium, etc.).
`premiumCapabilities`	Yes	Number of premium capabilities across all plugins.
`sessionContextPacket`	Yes	Machine-readable SAP MCP routing, freshness, memory, proof-tape, and forbidden-action rules for this session.
`skillsUpdateRequired`	Yes	True when the server version differs from agentKnownVersion (or agentKnownVersion was omitted). When true, skillsContents contains the full SKILL.md contents of all bundled skills.
`premiumProvidersReady`	Yes	Number of premium providers with configured environment variables.

TDQS

A4.7/5.0

Behavior5/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Annotations already provide readOnlyHint, idempotentHint, destructiveHint. The description adds meaningful behavioral context: it is 'free', returns a 'compact markdown-like summary', and details the agentKnownVersion behavior (skillsUpdateRequired + skillsContents when version differs). No contradictions with annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two paragraphs: first paragraph defines core purpose, lists outputs, explains agentKnownVersion feature, and directs away from siblings. Second paragraph provides execution guidance. Every sentence adds value with no wasted words. Front-loaded with most important info.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool's moderate complexity (5 parameters, 0 required, output schema exists) and rich annotations, the description covers all necessary aspects: purpose, usage, behavioral details, alternatives, execution guidance. No gaps identified.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100% with detailed parameter descriptions. The tool description mentions agentKnownVersion usage but adds no new meaning beyond the schema's own description. For parameters like intent, compact, include, and maxChars, the description provides no additional semantics. Baseline 3 is appropriate as schema carries the full burden.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description states it is a 'free single-call bootstrap aggregator' that returns a compact summary with specific data (server version, tools count, pricing, etc.). It clearly distinguishes itself by listing the five separate tools it replaces (sap_agent_start, sap_pricing_catalog, etc.), making the purpose specific and differentiated from siblings.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Explicitly advises 'Use this instead of calling sap_agent_start, sap_pricing_catalog, sap_premium_plugin_catalog, sap_skills_list, and sap_get_tool_category_summary separately to reduce bootstrap from 5+ tool calls to 1.' Provides clear context for when to use (bootstrap) and names alternatives. Also includes guidance on agentKnownVersion usage for auto-updating skills.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

All SAP MCP Server tools Inspect

Try in Browser

RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

Glama MCP Gateway

Add one secure layer between your agents and this server.

TDQS

B3.2/5.0

Disambiguation4/5

Tools are organized by protocol prefix (e.g., adrena_, jupiter_, sap_) which helps distinguish domains. Within each protocol, tool names clearly indicate actions (e.g., openPosition, getQuote). However, with 360 tools, some cross-protocol overlaps (e.g., multiple swap tools) and many similar fetch tools in the sap_* family require careful reading of descriptions to disambiguate.

Naming Consistency4/5

Each protocol group follows a consistent naming convention (e.g., snake_case for adrena_, camelCase for 3land, sap_ prefix for SAP SDK tools). The mix of conventions across protocols is acceptable, though a uniform style would improve predictability. Minor inconsistency: hyphenated names like metaplex-nft_ vs underscores.

Tool Count2/5

360 tools is far too many for a well-scoped MCP server. This aggregates dozens of protocols and SAP-specific features, making navigation difficult. The server would benefit from being split into focused micro-servers (e.g., SAP identity, Jupiter DEX, NFT tools). The current count overwhelms the coherence of the set.

Completeness4/5

The tool set covers a vast range of Solana ecosystem activities: token operations, swaps, staking, NFT management, bridging, oracle data, identity registration, chat, escrow, subscriptions, and premium streaming. Major lifecycle operations are present, though some niche subdomains may have missing functions (e.g., detailed governance or lending management). Overall, it's comprehensive for the intended scope.

SAP MCP Quick Context

Input Schema

Output Schema

TDQS

Glama MCP Gateway

TDQS

Resources