SAP MCP Server

SAP MCP Server is a hosted remote MCP service operated by OOBE Protocol. In this product name, SAP means Synapse Agent Protocol according to the provider, not the SAP SE enterprise resource planning product. The service exposes a Streamable HTTP MCP interface described on the official product page at https://mcp.sap.oobeprotocol.ai. Its documented remote endpoint is https://mcp.sap.oobeprotocol.ai/mcp. The provider machine profile identifies the service as SAP MCP Server, reports version 0.9.82 and online status, and names OOBE Protocol as the payment recipient. The exact Smithery entry oobe-protocol/sap-mcp is present as a remote deployed entry and explicitly maps its successful deployment to the upstream https://mcp.sap.oobeprotocol.ai/mcp. Smithery also uses the deployment endpoint https://sap-mcp--oobe-protocol.run.tools. This mapping is therefore supported by the provider source rather than only by a similar name or namespace.

Actual SAP and Solana scope

According to the provider, SAP MCP wraps Synapse Agent Protocol tools, Synapse AgentKit, the SAP agent registry, Solana RPC and token ecosystem functions, SNS identity, profiles, capabilities, payments, memory, sessions, and execution proofs. The published tool and OpenAPI descriptions additionally identify tools for Jupiter, Metaplex, Pump.fun, Raydium, Orca, perps analytics, NFT and DAS queries, and other Solana services. This is not a connector for SAP ERP tables, SAP company codes, customer masters, suppliers, personnel records, invoices, or conventional financial accounting. There is therefore no sound basis for describing it as an enterprise ERP integration or as a source of official business or personal data.

The data sources are described by the provider as public or connected Solana RPC, indexing, market, routing, and Synapse services, together with on-chain accounts and protocol state. These sources are not automatically authoritative, complete, or immutable. RPC responses, market prices, balances, ownership assertions, identity data, reputation values, memory contents, and transaction status should be checked before consequential use with the network, timestamp, asset identity, signature, and an independent source. Data may include wallet addresses, public agent profiles, capabilities, payment and transaction references, session data, and user-submitted content. Do not submit personal or confidential enterprise information.

Authorization, roles, and privacy

The official server description identifies a public mode that may initially be bearerless and x402 payment proofs for paid calls. According to the provider, private beta, enterprise, and administrative deployments can use API keys or JWT bearer authentication. The Smithery configuration also describes free discovery, an x402-capable client, and a local payment bridge. The visible tools depend on the deployment, session, payment authorization, local policy, and actual permission scope. A publicly reachable endpoint is not authorization for private accounts or other wallets and is not ERP-style tenant separation.

OOBE describes a non-custodial architecture in which user keypairs remain local or behind an external signer rather than being uploaded to the hosted service. The service can nevertheless process requests, public keys, wallet and agent references, payment proofs, tool results, sessions, usage, and error data. The documentation describes session, usage, memory, audit, and observability functions, as well as configurable deployment logs and retention, but the reviewed public sources do not state one generally binding retention period or complete sharing policy for this public service. Assess the provider, Smithery, client, model provider, RPC, indexing, and payment services separately. The repository MIT license is not a security, privacy, or compliance guarantee.

Write and consequential actions

The documented surface includes more than reads and discovery. According to the provider, it can include agent registration and profile updates, payments, settlement, memory and session changes, preparation and finalization of signed transactions, transfers, token and NFT actions, swaps, purchases, sales, minting, burning, and other protocol operations. These capabilities can incur fees or move assets and are not equivalent to creating, changing, deleting, approving, posting, ordering, or invoicing in SAP ERP. Smithery and the provider documentation describe a free discovery path and a separate local payment and signing bridge for paid or write workflows. Enable write tools only with least-privilege roles, bounded amounts, fixed destinations, and explicit human approval. Verify raw parameters, network, fees, slippage, signature, and result outside the language model. Prompt injection, wrong asset selection, stale RPC data, compromised API keys, and unclear third-party sources remain risks.

The official OOBE-PROTOCOL/sap-mcp repository is public and released under the MIT license; it contains local stdio, remote, wizard, payment, and security components. The hosted service, connected data sources, and their content may be subject to additional terms. The service is independently catalog-worthy on a durable basis because its product page, documentation, repository, license, operator identity, and endpoint form a traceable match. This entry does not certify on-chain data accuracy or the security of a particular deployment. Human review and explicit confirmation are required before signing, paying, writing, settlement, or any other irreversible operation.

FAQ

Is SAP MCP an SAP ERP integration? No. According to the provider, SAP means Synapse Agent Protocol, and the functionality targets Solana and agent protocols rather than SAP SE business systems.

What data is processed? Depending on the tool, public on-chain, wallet, agent, identity, market, payment, session, and tool data, plus user-submitted inputs. Private keys are intended to remain local; confidential data should not be sent to the service.

Can it write or trigger transactions? Yes. The repository and documentation describe registry, payment, signing, and value-relevant tools. They require appropriate local or external authorization and explicit human review before execution.

How long is data retained? The reviewed sources do not establish one public retention period applying to all users. Check the applicable provider, deployment, client, model, and third-party terms.

An MCP-compatible client for Streamable HTTP. The documented remote endpoint supports read scenarios; paid or write workflows may require x402 and a local payment bridge or external signer.

Add the official remote endpoint https://mcp.sap.oobeprotocol.ai/mcp to the MCP client and follow the provider documentation for sessions, payment mode, and local signing. Keep write tools disabled by default and confirm each execution separately.

According to the provider, public mode can support bearerless discovery, x402 covers paid calls, and API keys or JWT support private, enterprise, and administrative modes. Authorization applies only to the granted account and role scope.

Read access to Synapse Agent Protocol, Solana, identity, market, and session data; depending on deployment, additional registry, payment, memory, signing, transfer, swap, NFT, and other value-relevant write actions.

Remote requests and results may contain wallet, agent, identity, payment, session, usage, and tool data. The provider describes local key custody, but no single public retention period or complete sharing policy for every involved service.

Prompt injection, overprivileged keys, wrong wallet or asset selection, stale RPC and market information, payment and signing errors, and irreversible protocol actions. Block write tools and require human review before consequential effects.