{
  "markdown": "# SAP MCP Server\n\nProduction-oriented Model Context Protocol server for OOBE Synapse Agent Protocol, Solana, Synapse AgentKit, SNS, and monetized hosted agent workflows.\n\nSAP MCP exposes the same typed tool registry through two supported MCP launch modes:\n\n1. Local stdio for desktop agents and local development.\n2. Remote Streamable HTTP at `/mcp` for hosted customers and orchestrators.\n\nIt also includes a professional setup wizard, profile-managed config under `~/.config/mcp-sap`, optional Bento policy integration, local and external signing modes, x402 monetization, a self-hosted OOBE facilitator, pay.sh provider YAML generation, and an A2A-compatible discovery card.\n\nUser-facing setup docs live in [`USER_DOCS/`](USER_DOCS/00_USER_ONBOARDING_INDEX.md). Operator and engineering docs live in [`docs/`](docs/00_ENGINEERING_DOCUMENTATION_INDEX.md).\n\n## 1. Status\n\n| Area | Current behavior |\n| --- | --- |\n| Package version | `0.9.80` |\n| MCP transport | stdio locally, Streamable HTTP remotely |\n| Remote access | Bearerless public mode for hosted agents; API key or JWT for private modes |\n| Config directory | `~/.config/mcp-sap` only |\n| Agent wallet | Dedicated wallet path under `~/.config/mcp-sap/keypairs/` by default |\n| Solana CLI keypair | Never modified by the wizard |\n| Policy | Local policy by default, optional Bento or hybrid policy |\n| Monetization | Optional remote-only x402/pay.sh payment flow with per-tool pricing |\n| Signing | Local dedicated wallet or external signer, depending on profile mode |\n| Discovery | A2A-compatible card at `/.well-known/agent-card.json` |\n\n## 2. Install\n\nPrerequisites:\n\n```bash\nnode --version   # >= 22.12.0\ncorepack enable\ncorepack prepare pnpm@11.7.0 --activate\npnpm --version   # 11.7.0\n```\n\nFrom source:\n\n```bash\npnpm install\npnpm run build\n```\n\nDo not use `npm install` for source deployments. This repository is locked and verified with pnpm.\n\nFrom the published package:\n\n```bash\nnpm install -g @oobe-protocol-labs/sap-mcp-server\n```\n\n## 3. Quick Start\n\nCreate or select a profile:\n\n```bash\nnpx sap-mcp-config wizard\n```\n\nRepair hosted SAP MCP runtime entries without recreating the profile:\n\n```bash\nnpx sap-mcp-config repair\n```\n\nAfter connecting hosted SAP MCP in an agent runtime, start the agent context\nwith one short message:\n\n```text\nStart SAP MCP.\n```\n\nThe agent should call the free `sap_agent_start` tool or `sap-agent-start`\nprompt, load `sap_skills_bundle`, and use the local `sap_payments` bridge for\npaid/write hosted calls.\n\nInspect the active profile:\n\n```bash\nnpx sap-mcp-config show\nnpx sap-mcp-config doctor\nnpx sap-mcp-config pubkey\nnpx sap-mcp-config profiles\n```\n\nStart local stdio MCP:\n\n```bash\nsap-mcp-server\n```\n\nor from source:\n\n```bash\nnode dist/cli.js\n```\n\nHosted customers connect their agents to `https://mcp.sap.oobeprotocol.ai/mcp`, but signing remains user-controlled. The recommended setup for most users is the wizard-managed pair of MCP entries:\n\n- `sap`: hosted Streamable HTTP SAP MCP at `https://mcp.sap.oobeprotocol.ai/mcp`;\n- `sap_payments`: local non-custodial payment bridge for x402/pay.sh paid/write calls.\n\nAny user who wants to pay x402/pay.sh charges, register or operate a SAP identity, or execute value-moving Solana/SAP tools should run the wizard first and keep the dedicated wallet under `~/.config/mcp-sap/keypairs/` or behind an external signer. Read-only hosted discovery can use the remote URL without a local signer.\n\n## 4. Local Client Config\n\nFor local agents, let SAP MCP follow the active profile manager instead of hard-coding wallet paths or stale RPC overrides:\n\n```json\n{\n  \"mcpServers\": {\n    \"sap\": {\n      \"command\": \"sap-mcp-server\",\n      \"env\": {\n        \"SAP_MCP_ALLOW_ENV_CONFIG_OVERRIDE\": \"false\",\n        \"SAP_LOG_LEVEL\": \"info\"\n      }\n    }\n  }\n}\n```\n\nCodex uses TOML rather than the JSON `mcpServers` shape. For hosted remote MCP, add this to `~/.codex/config.toml` and restart Codex:\n\n```toml\n[mcp_servers.sap]\nurl = \"https://mcp.sap.oobeprotocol.ai/mcp\"\n```\n\nFor paid/write hosted tools, add the local non-custodial payment bridge as well:\n\n```toml\n[mcp_servers.sap_payments]\ncommand = \"npx\"\nargs = [\"--yes\", \"--package\", \"@oobe-protocol-labs/sap-mcp-server@0.9.80\", \"sap-mcp-server\"]\nstartup_timeout_sec = 300\ntool_timeout_sec = 300\n\n[mcp_servers.sap_payments.env]\nSAP_MCP_ALLOW_ENV_CONFIG_OVERRIDE = \"false\"\nSAP_MCP_PAYMENTS_BRIDGE_ONLY = \"true\"\nSAP_ALLOWED_TOOLS = \"all\"\nSAP_LOG_LEVEL = \"info\"\n```\n\nOn Windows, use `command = \"npx.cmd\"`. The wizard can write this automatically.\n\nCodex supports Streamable HTTP MCP servers with URL-based entries in `config.toml`. Use local stdio through `npx` only when you specifically want Codex to launch the local SAP MCP process:\n\n```toml\n[mcp_servers.sap]\ncommand = \"npx\"\nargs = [\"--yes\", \"--package\", \"@oobe-protocol-labs/sap-mcp-server@0.9.80\", \"sap-mcp-server\"]\n\n[mcp_servers.sap.env]\nSAP_MCP_ALLOW_ENV_CONFIG_OVERRIDE = \"false\"\nSAP_LOG_LEVEL = \"info\"\n```\n\nOn Windows, use `command = \"npx.cmd\"`.\n\nSee [04. Local Stdio MCP Runbook](docs/04_LOCAL_STDIO_MCP_RUNBOOK.md).\n\n## 5. Remote Server\n\nRemote deployments expose MCP over Streamable HTTP:\n\n```bash\nnode dist/remote/server.js\n```\n\nProduction environment values should come from a private secret store or private deployment file, not from public docs. Public hosted agent-facing deployments can use `SAP_MCP_AUTH_TYPE=none` when x402, rate limits, and policy are enabled. API key or JWT auth remains available for private beta, enterprise, and admin deployments.\n\nRemote endpoints:\n\n```text\nGET     /\nGET     /docs\nGET     /server.json\nGET     /favicon.png\nGET     /favicon.ico\nGET     /health\nGET     /openapi.json\nGET     /.well-known/x402\nGET     /pay/provider.yml\nGET     /.well-known/agent-card.json\nGET     /.well-known/sap-mcp-wizard.json\nGET     /.well-known/sap-mcp-tool-catalog.json\nGET     /tool-catalog.json\nGET     /wizard/install.sh\nPOST    /mcp\nGET     /mcp\nDELETE  /mcp\n```\n\n`GET /` is a public, share-safe landing page with Open Graph/Twitter metadata. It exposes only public server information; keypair bytes, private wallet paths, RPC query secrets, and VPS-local paths must never appear there.\n\n`GET /docs` serves the public documentation site for install, start, configuration, hosted remote MCP, x402/pay.sh payments, and MCP client setup.\n\nMarketplace listings such as Smithery can use [`smithery.config.schema.json`](smithery.config.schema.json)\nto explain the hosted setup path. The schema intentionally asks for no\nsecrets: SAP MCP hosted reads work remotely, while paid/write calls use the\nwizard-managed local `sap_payments` bridge, local profile policy, and\nuser-controlled signer.\n\nSee [05. Hosted Streamable HTTP Deployment](docs/05_HOSTED_STREAMABLE_HTTP_DEPLOYMENT.md) and [07. HTTP Endpoints, MCP Clients, And Smoke Tests](docs/07_HTTP_ENDPOINTS_MCP_CLIENTS_SMOKE_TESTS.md).\n\n## 6. Monetization\n\nHosted HTTP deployments can require payment for paid `tools/call` requests while leaving local stdio and base MCP protocol calls free.\n\nInitial model:\n\n| Tier | Examples | Price |\n| --- | --- | --- |\n| Free | `tools/list`, `prompts/list`, `resources/list`, bootstrap/status/repair, cost estimation, local payment bridge control, SOL/SPL/x402 balance readiness, single-asset price snapshots, memory/audit, transaction preview/finalize helpers | Free |\n| Micro read | exact agent/profile reads, compact directory pages, SNS availability, escrow state, lightweight trader context | `$0.001` |\n| Premium read | broad discovery, enriched holdings/DAS, token lists, quotes/routes, history/OHLCV, analytics, larger pages | `$0.002` |\n| Builder or batch | complex builders, SNS/domain batch checks, unsigned transaction builders, routing preparation | `$0.006`, batch = sum of paid calls |\n| Value action | selected value-linked operations | fixed `$0.06` standard, `$0.035` selected heavy paths, plus optional bps |\n\nEnable x402:\n\n```bash\nSAP_MCP_MONETIZATION_ENABLED=true\nSAP_MCP_MONETIZATION_PROVIDER=x402\nSAP_MCP_MONETIZATION_PAY_TO=YOUR_SOLANA_USDC_RECIPIENT\nSAP_MCP_X402_FACILITATOR_URL=YOUR_PRIVATE_OR_HOSTED_FACILITATOR_URL\n```\n\nInitialize and run the OOBE facilitator:\n\n```bash\nnpx sap-mcp-facilitator init\nnpx sap-mcp-facilitator start\n```\n\nGenerate a pay.sh provider YAML:\n\nThe hosted public catalog is available at `https://mcp.sap.oobeprotocol.ai/pay/provider.yml`.\nIt is secret-free and intended for pay.sh catalog/proxy discovery.\n\n```bash\nnpx sap-mcp-pay-sh-spec \\\n  --out sap-mcp-pay-sh.yml \\\n  --upstream-url https://mcp.sap.oobeprotocol.ai \\\n  --network mainnet \\\n  --recipient YOUR_SOLANA_USDC_RECIPIENT\n```\n\nSee [06. x402/pay.sh Monetization Settlement](docs/06_X402_PAYSH_MONETIZATION_SETTLEMENT.md).\n\nFor local agent runtimes that cannot replay x402 challenges natively, install\nthe wizard's local `sap_payments` bridge and call `sap_payments_call_paid_tool`.\nThe legacy CLI helper is still available for terminal use:\n\n```bash\nnpm exec --yes --package @oobe-protocol-labs/sap-mcp-server -- sap-mcp-x402-paid-call \\\n  --tool sap_list_all_agents \\\n  --arguments '{\"limit\":5}' \\\n  --max-usd 0.02 \\\n  --confirm\n```\n\nThe helper signs payment payloads with the user's local SAP MCP profile and\nnever sends keypair bytes to the hosted server.\n\n## 7. Commands\n\n```bash\npnpm run typecheck\npnpm run lint\npnpm test -- --run\npnpm run build\npnpm run verify:release\n```\n\nInstalled binaries:\n\n| Command | Purpose |\n| --- | --- |\n| `sap-mcp-server` | Local stdio MCP server and CLI entry point |\n| `sap-mcp-remote` | Remote MCP server with bearerless, API key, and JWT modes |\n| `sap-mcp-config` | Config CLI, profile manager, approval workflow, and wizard |\n| `sap-mcp-wizard` | TUI configuration wizard |\n| `sap-signing-proxy` | Local signing proxy |\n| `sap-mcp-facilitator` | Self-hosted x402 SVM facilitator |\n| `sap-mcp-pay-sh-spec` | pay.sh provider YAML generator |\n| `sap-mcp-x402-paid-call` | Legacy terminal/custom-wrapper fallback for hosted x402 paid MCP tools |\n\n## 8. Documentation\n\nStart with [00. Engineering Documentation Index](docs/00_ENGINEERING_DOCUMENTATION_INDEX.md).\n\n| Document | Purpose |\n| --- | --- |\n| [01. Product Scope Deployment Model](docs/01_PRODUCT_SCOPE_DEPLOYMENT_MODEL.md) | Product model, users, public/private repo guidance, and wizard distribution. |\n| [02. Runtime Architecture Trust Boundaries](docs/02_RUNTIME_ARCHITECTURE_TRUST_BOUNDARIES.md) | Runtime modules, local flow, remote flow, signing, payments, and trust boundaries. |\n| [03. Profile Config Wizard Injection](docs/03_PROFILE_CONFIG_WIZARD_INJECTION.md) | Profile manager, wizard, wallet isolation, client injection, and config CLI. |\n| [04. Local Stdio MCP Runbook](docs/04_LOCAL_STDIO_MCP_RUNBOOK.md) | Local setup for Claude, Hermes, Codex, OpenClaw, and development agents. |\n| [05. Hosted Streamable HTTP Deployment](docs/05_HOSTED_STREAMABLE_HTTP_DEPLOYMENT.md) | Hosted deployment, reverse proxy, PM2, and customer onboarding. |\n| [06. x402/pay.sh Monetization Settlement](docs/06_X402_PAYSH_MONETIZATION_SETTLEMENT.md) | Pricing, x402 gate, pay.sh provider YAML, facilitator signer, and settlement. |\n| [07. HTTP Endpoints, MCP Clients, And Smoke Tests](docs/07_HTTP_ENDPOINTS_MCP_CLIENTS_SMOKE_TESTS.md) | HTTP endpoints, headers, smoke tests, and client examples. |\n| [08. Security Policy Signing Runbook](docs/08_SECURITY_POLICY_SIGNING_RUNBOOK.md) | Key material rules, signer modes, Bento policy, and transaction safety. |\n| [09. Tool Skill Routing Agent Operations](docs/09_TOOL_SKILL_ROUTING_AGENT_OPERATIONS.md) | Tool families, SDK doc pointers, skills, and agent behavior. |\n| [10. Release Operations PM2 Runbook](docs/10_RELEASE_OPERATIONS_PM2_RUNBOOK.md) | Quality gates, PM2, secrets, release packaging, and changelog discipline. |\n| [11. Engineering Quality Audit Report](docs/11_ENGINEERING_QUALITY_AUDIT_REPORT.md) | Current engineering scorecard, release gates, quality rules, and residual risks. |\n| [12. Signed Agent Chat Protocol](docs/12_SIGNED_AGENT_CHAT_PROTOCOL.md) | Signed thematic group chat, room manifests, retrieval, link sharing, privacy boundaries, and SDK roadmap. |\n| [13. Bounty Program Technical Spec](docs/13_BOUNTY_PROGRAM_TECHNICAL_SPEC.md) | Partner bounty scope, judging criteria, and technical requirements. |\n| [14. Desktop Wizard Release Artifacts](docs/14_DESKTOP_WIZARD_RELEASE_ARTIFACTS.md) | Native wizard packaging, signing, checksums, and release artifacts. |\n| [15. Demo Dashboard Screenshare Runbook](docs/15_DEMO_DASHBOARD_SCREENSHARE_RUNBOOK.md) | Demo flow for hosted landing page, dashboard, wizard, and payment surfaces. |\n| [16. Agent Identity Registry Pipeline](docs/16_AGENT_IDENTITY_REGISTRY_PIPELINE.md) | Registry source truth, enrichment, validation, and display pipeline. |\n| [18. Premium Plugin Runtime Contracts](docs/18_PREMIUM_PLUGIN_RUNTIME_CONTRACTS.md) | Premium plugin manifest contracts, provider readiness, streams, and webhooks. |\n| [19. Agentic Standards Interoperability](docs/19_AGENTIC_STANDARDS_INTEROPERABILITY.md) | MCP, A2A, marketplace, x402/pay.sh, and runtime alignment. |\n| [20. Engineering Operating Model Boundaries](docs/20_ENGINEERING_OPERATING_MODEL_BOUNDARIES.md) | Branch ownership, service contracts, release personas, and company-grade gates. |\n\n## 9. Repository Layout\n\nThe repository is a modular monorepo. Real source code lives in `packages/*/src/`; the corresponding `src/` directories are thin compatibility wrappers (`export * from '../../packages/...'`) that preserve existing import paths.\n\n```text\npackages/\n  core/              Shared runtime types, errors, logger, constants, guards, result\n  config-runtime/    Runtime config, secure config manager, setup wizard, runtime doctor, client injection\n  server-runtime/    MCP server factory, capability registration, server metadata\n  hosted-gateway/    Streamable HTTP MCP server, public home, premium routes, rate limiter, tx relay\n  local-bridge/      Local stdio MCP bridge, payment bridge process diagnostics\n  mcp-adapter/       Model Context Protocol adapter compatibility layer\n  schemas/           Public Zod schemas and protocol contracts\n  tools/             SAP, Solana, AgentKit, SNS, profile, skill, chat, payment, perps, and premium tools\n  ui-cards/          MCP Apps Card rendering, card builder, templates, protocol logos\n  wizard-core/       Shared CLI and desktop wizard flow\n  tool-plugin-template/  Trusted external tool-family plugin template\n  adapters/          Solana connection and public key adapter utilities\n  bin/               npx-safe bootstrap entrypoints for remote and local servers\n  memory/            Agent memory store, tool call store, stream buffer, Hermes bridge\n  observability/     Metrics collection and exporter\n  perps/             Perpetual futures analytics, Adrena builders, chart indicators, risk engine\n  payments/          x402 monetization, facilitator, usage ledger, pay.sh spec, pricing\n  policy/            Local, Bento, and hybrid policy engines, spending limits, permission checks\n  premium/           Premium runtime plugins, streams, webhooks, session management\n  prompts/           MCP prompt templates for developer, payments, context, execution-proof, registry\n  resources/         MCP resource templates for memory, execution-proof, reputation, profile, registry, stats\n  runtime/           Module resolution and payment bridge process management\n  sap/               SAP SDK client manager, types, and error classes\n  security/          Private-key guard, tool permissions, prompt injection notes, approval gates\n  session/           Session store, delegated sessions, agent sessions, session limits\n  signer/            Local, delegated, and external signer adapters, wallet guard, policy-enforcing wallet\n  solana/            Solana ATA utilities\n  strategies/        Strategy store and trade journal\n  transports/        stdio and HTTP transport layers\n  tui/               Terminal UI wizard save helper (legacy, source in src/tui/)\n```\n\nThe root `package.json` re-exports all package surfaces so consumers can import from `@oobe-protocol-labs/sap-mcp-server` without referencing internal packages directly.\n\n## 10. License\n\nSAP MCP Server is released under the [MIT License](LICENSE).\n\n## 11. Partner Products\n\n| Partner / Product | Integration |\n| --- | --- |\n| [@bentoguard / Bento Guard](https://github.com/bentoguard) | Optional policy layer for AI-assisted intent scoring, escalation, and hybrid local/Bento guardrails. Uses the optional `@bentoguard/sdk` package and credentials from [app.bentoguard.xyz](https://app.bentoguard.xyz). |\n",
  "bytes": 16563,
  "sha": "5b5aeeb890a53386ff5e0835fbb9b979ada9072ab9b5d45e5a6f4f08cd9d21d8",
  "repo_slug": "oobe-protocol/sap-mcp",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_ai_oobeprotocol_sap_mcp_sap_mcp_6f373c80/readme"
}