SAP MCP Server

What SAP MCP Server MCP server does

SAP MCP Server MCP server exposes a typed MCP tool registry for OOBE Synapse Agent Protocol and Solana-oriented agent workflows. The project covers Synapse AgentKit, SNS identity, hosted agent discovery, x402 payments, and selected value-linked operations. It is not limited to one connection mode: local agents can launch it over stdio, while hosted customers and orchestrators can use Streamable HTTP.

The registry includes free bootstrap and status operations, skill loading, configuration and repair helpers, payment-bridge control, balance readiness checks, asset price snapshots, memory and audit functions, transaction preview and finalize helpers, discovery, profile reads, SNS availability checks, escrow state, holdings, token lists, quotes, routes, history, analytics, and builder or batch operations. Exact availability and pricing depend on the deployment and tool category.

How it works

A local process starts with sap-mcp-server or node dist/cli.js and reads the active profile managed under ~/.config/mcp-sap. Remote deployments run an HTTP server with MCP requests at /mcp; the hosted endpoint documented by the project is https://mcp.sap.oobeprotocol.ai/mcp. Remote deployments can use bearerless public access, API keys, or JWT authentication depending on the mode.

Signing remains user-controlled. The default dedicated wallet is stored below ~/.config/mcp-sap/keypairs/, while external signer profiles are also supported. Read-only hosted discovery can work without a local signer. Paid or write-oriented hosted calls use the separate local sap_payments bridge, which can replay x402 or pay.sh payment flows for runtimes that do not handle those challenges directly.

Setup and configuration

Use Node.js 22.12.0 or newer, enable Corepack, and use pnpm 11.7.0 for source installations. Build from source with pnpm install followed by pnpm run build, or install the published package globally with npm. The project advises against using npm for source deployments.

Run npx sap-mcp-config wizard to create or select a profile. The same utility can repair hosted runtime entries, display the active profile, run diagnostics, list profiles, and show the configured public key. The wizard can configure the hosted sap entry and the local sap_payments bridge for clients such as Codex.

Tools and capabilities

SAP MCP Server MCP server supports an agent-start bootstrap flow through sap_agent_start or the sap-agent-start prompt, followed by loading sap_skills_bundle. Its payment bridge exposes sap_payments_call_paid_tool for paid hosted calls. The remote service also publishes health, OpenAPI, tool-catalog, payment-provider, and A2A-compatible discovery endpoints.

Optional monetization uses x402 and can generate a pay.sh provider YAML file. Deployments may assign different prices to lightweight reads, enriched discovery, builders, batches, and value-linked actions. The project also includes a self-hosted OOBE facilitator for settlement workflows.

Limitations and notes

The hosted URL is remote-only and does not replace the local signer needed for paid, identity, or value-moving workflows. Keep wallet files and deployment secrets private; public endpoints are intended to expose server metadata rather than key material or local paths. Remote monetization is optional, and local stdio plus base MCP protocol calls may remain free even when hosted tool calls require payment.

The configuration manager uses ~/.config/mcp-sap; the README states that the wizard does not modify the Solana CLI keypair. Client configuration differs by runtime: JSON-style mcpServers entries apply to many local clients, while Codex uses TOML. On Windows, the documented local command uses npx.cmd instead of npx.