# sap-mcp Server

> Use the SAP MCP Wizard or install the library from the npm registry to automatically create and configure a Solana/SAP wallet via https://mcp.sap.oobeprotocol.a

- Price: Free to connect · provider's own fees apply
- URL: https://daas.listeningmind.ai/en/catalog/mcps/x-mcp-oobe-protocol-sap-mcp
- Source: Smithery https://smithery.ai/server/oobe-protocol/sap-mcp
- Rank this week: #37 (score 57)

## Install

```
npx -y @smithery/cli install oobe-protocol/sap-mcp --client claude
```
- `usageMode` (optional): Use free-discovery for immediate hosted reads that do not require payment. Use x402-native-client when this runtime can parse PAYMENT-REQUIRED and retry with PAYMENT-SIGNATURE or X-PAYMENT.
- `x402Payer` (optional): How paid MCP calls will be paid. Select none for free discovery only, native when the current client signs x402 itself, sap-payments when the local SAP MCP bridge is installed, or custom when an exter…
- `setupCommand` (optional): Copy this command into a local terminal when paid/write tools should work from a non-custodial user profile.
- `submitRelayUrl` (optional): Optional submit-only relay for already-signed Solana transactions returned by local sappaymentsfinalizetransaction. The relay never signs and never receives keypair bytes.
- `wizardCompleted` (optional): Set true after running the SAP MCP wizard locally: npm exec --yes --package @oobe-protocol-labs/sap-mcp-server -- sap-mcp-config wizard.
- `maxUsdPerPaidCall` (optional): Recommended local policy cap for x402/pay.sh hosted paid tool calls. The hosted server returns the challenge; the local sappayments bridge, native x402 client, or custom payer should enforce this cap…
- `autoPayMicropayments` (optional): Optional local/client behavior for tiny approved calls under the configured cap. OOBE hosted MCP never stores user keypairs, wallet bytes, or signer secrets.
- Remote: https://sap-mcp--oobe-protocol.run.tools

## Tools (275)

- `sap_protocol_invariants`: Free read-only protocol invariant card for agents. Returns the current SAP program id, protocol treasury, source-level expected 0.1 SOL registration fee invariant, hosted write rou…
- `sap_agent_identity_plan`: Free read-only planner for SAP agent registration, profile/image updates, Metaplex/MPL Core identity linking, SNS linking, x402 pricing metadata, and post-write verification.
- `sap_register_agent`: Deprecated raw SDK wrapper. Production registration must use sappaymentsregisteragent so the local signer path confirms the account, verifies the 0.1 SOL protocol treasury fee inva…
- `sap_update_agent`: Local-signer-only: update the connected wallet SAP agent using SDK AgentModule.update.
- `sap_deactivate_agent`: Deactivate the connected wallet SAP agent. SAP MCP context: Direct synapse-sap-sdk wrapper served by this MCP.
- `sap_reactivate_agent`: Reactivate the connected wallet SAP agent. SAP MCP context: Direct synapse-sap-sdk wrapper served by this MCP.
- `sap_close_agent`: Close the connected wallet SAP agent and reclaim rent. SAP MCP context: Direct synapse-sap-sdk wrapper served by this MCP.
- `sap_report_calls`: Report served call count for the connected wallet SAP agent. SAP MCP context: Direct synapse-sap-sdk wrapper served by this MCP.
- `sap_update_reputation_metrics`: Update self-reported latency and uptime metrics for the connected wallet SAP agent. SAP MCP context: Reputation and trust flow.
- `sap_get_agent`: Fetch agent identity by owner wallet. If omitted, fetches the connected wallet agent. SAP MCP context: Read-only SAP SDK wrapper against the configured Solana RPC and SAP program.
- `sap_get_agent_stats`: Fetch agent stats by agent PDA. SAP MCP context: Read-only SAP SDK wrapper against the configured Solana RPC and SAP program.
- `sap_get_global_state`: Fetch the on-chain global registry through SDK AgentModule.fetchGlobalRegistry. SAP MCP context: Read-only SAP SDK wrapper against the configured Solana RPC and SAP program.
- `sap_get_network_overview`: Fetch real network counters from SDK DiscoveryRegistry.getNetworkOverview. SAP MCP context: Read-only SAP SDK wrapper against the configured Solana RPC and SAP program.
- `sap_get_agent_profile`: Fetch a hydrated SAP agent profile by owner wallet. SAP MCP context: Read-only SAP SDK wrapper against the configured Solana RPC and SAP program.
- `sap_is_agent_active`: Check if a wallet owns an active SAP agent. SAP MCP context: Read-only SAP SDK wrapper against the configured Solana RPC and SAP program.
- `sap_discover_agents`: Paid hosted discovery for SAP agents. Search and filter the current on-chain AgentAccount directory by query, wallet, protocol, capability, x402 endpoint presence, and cursor pagin…
- `sap_list_agents`: Compatibility alias for sapdiscoveragents. Supports query, wallet, protocol, capability, x402 endpoint filtering, and cursor pagination.
- `sap_list_all_agents`: Paid hosted global SAP agent directory read. Enumerates current on-chain AgentAccount PDAs and supports query, wallet, protocol, capability, x402 endpoint filtering, compact/full v…
- `sap_find_tools_by_category`: Find on-chain tool descriptors by SDK tool category name or numeric category. SAP MCP context: Read-only SAP SDK wrapper against the configured Solana RPC and SAP program.
- `sap_get_tool_category_summary`: Fetch SDK discovery summary across SAP tool categories. SAP MCP context: Read-only SAP SDK wrapper against the configured Solana RPC and SAP program.
- `sap_fetch_capability_index`: Fetch a SAP capability index by capability ID. SAP MCP context: Read-only SAP SDK wrapper against the configured Solana RPC and SAP program.
- `sap_fetch_protocol_index`: Fetch a SAP protocol index by protocol ID. SAP MCP context: Read-only SAP SDK wrapper against the configured Solana RPC and SAP program.
- `sap_fetch_tool_category_index`: Fetch a SAP tool category index by numeric category. SAP MCP context: Read-only SAP SDK wrapper against the configured Solana RPC and SAP program.
- `sap_fetch_tool`: Fetch a tool descriptor by agent PDA and tool name. SAP MCP context: Read-only SAP SDK wrapper against the configured Solana RPC and SAP program.
- `sap_fetch_feedback`: Fetch a feedback PDA by agent PDA and optional reviewer wallet. SAP MCP context: Read-only SAP SDK wrapper against the configured Solana RPC and SAP program.
- `sap_fetch_attestation`: Fetch an attestation PDA by agent PDA and optional attester wallet. SAP MCP context: Read-only SAP SDK wrapper against the configured Solana RPC and SAP program.
- `sap_fetch_escrow`: Fetch a V1 escrow by escrow PDA, or by agent PDA and optional depositor. SAP MCP context: Read-only SAP SDK wrapper against the configured Solana RPC and SAP program.
- `sap_fetch_escrow_v2`: Fetch a V2 escrow by escrow PDA, or by agent PDA, depositor, and nonce. SAP MCP context: Read-only SAP SDK wrapper against the configured Solana RPC and SAP program.
- `sap_fetch_pending_settlement`: Fetch a V2 pending settlement PDA. SAP MCP context: Read-only SAP SDK wrapper against the configured Solana RPC and SAP program.
- `sap_fetch_dispute`: Fetch a V2 dispute PDA. SAP MCP context: Read-only SAP SDK wrapper against the configured Solana RPC and SAP program.
- `sap_fetch_vault`: Fetch a memory vault by agent PDA. SAP MCP context: Read-only SAP SDK wrapper against the configured Solana RPC and SAP program.
- `sap_fetch_session`: Fetch a session ledger by session PDA. SAP MCP context: Read-only SAP SDK wrapper against the configured Solana RPC and SAP program.
- `sap_fetch_epoch_page`: Fetch an epoch page by session PDA and epoch index. SAP MCP context: Read-only SAP SDK wrapper against the configured Solana RPC and SAP program.
- `sap_fetch_stake`: Fetch agent stake by stake PDA or agent PDA. SAP MCP context: Read-only SAP SDK wrapper against the configured Solana RPC and SAP program.
- `sap_fetch_subscription`: Fetch a subscription by PDA or by agent PDA/subscriber/subId. SAP MCP context: Read-only SAP SDK wrapper against the configured Solana RPC and SAP program.
- `sap_x402_estimate_cost`: Estimate cost for a number of calls using SDK X402Registry.estimateCost. Reads escrow/pricing when available and supports optional volume curve overrides.
- `sap_x402_calculate_cost`: Pure local cost calculation using SDK X402Registry.calculateCost; does not read chain state. SAP MCP context: Payment and settlement flow.
- `sap_x402_prepare_payment`: Prepare an x402 payment context using SDK X402Registry.preparePayment. New production escrow funding should use Escrow V2 fields and nonce-aware flows.
- `sap_x402_build_payment_headers`: Build SAP x402 HTTP headers from a public PaymentContext returned by sapx402preparepayment. SAP MCP context: Payment and settlement flow.
- `sap_x402_build_headers_from_escrow`: Build SAP x402 HTTP headers by fetching escrow data for an agent wallet with SDK X402Registry.buildPaymentHeadersFromEscrow. SAP MCP context: Payment and settlement flow.

## FAQ

### What is the sap-mcp Server?

Use the SAP MCP Wizard or install the library from the npm registry to automatically create and configure a Solana/SAP wallet via https://mcp.sap.oobeprotocol.a. It is listed on Smithery and ranks #37 (score 57) in ListeningMind.AI's weekly picks.

### How do I install the sap-mcp Server?

Run npx -y @smithery/cli install oobe-protocol/sap-mcp --client claude in a terminal to add it to Claude Desktop. For Cursor, use --client cursor.

### Do I need an API key?

The provider lists no required settings.

### Which tools does it provide?

275 tools: sap_protocol_invariants, sap_agent_identity_plan, sap_register_agent, sap_update_agent, sap_deactivate_agent, sap_reactivate_agent, sap_close_agent, sap_report_calls, sap_update_reputation_metrics, sap_get_agent, sap_get_agent_stats, sap_get_global_state.

### How much does it cost?

Free to connect · provider's own fees apply. The provider may charge for use on its own terms.

### Can I trust it?

Checks passed: In the official MCP Registry, Own homepage, Live endpoint, Clear description. Skim a server or repository you have not used before connecting it.