SAP MCP Server

Production-oriented Model Context Protocol server for OOBE Synapse Agent Protocol, Solana, Synapse AgentKit, SNS, and monetized hosted agent workflows.

SAP MCP exposes the same typed tool registry through two supported MCP launch modes:

1. Local stdio for desktop agents and local development.
2. Remote Streamable HTTP at /mcp for hosted customers and orchestrators.

It 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.

1. Status

Area	Current behavior
Package version	0.1.1
MCP transport	stdio locally, Streamable HTTP remotely
Remote access	Bearerless public mode for hosted agents; API key or JWT for private modes
Config directory	~/.config/mcp-sap only
Agent wallet	Dedicated wallet path under ~/.config/mcp-sap/keypairs/ by default
Solana CLI keypair	Never modified by the wizard
Policy	Local policy by default, optional Bento or hybrid policy
Monetization	Optional remote-only x402/pay.sh payment flow with per-tool pricing
Signing	Local dedicated wallet or external signer, depending on profile mode
Discovery	A2A-compatible card at /.well-known/agent-card.json

2. Install

From source:

pnpm install
pnpm run build

From the published package:

npm install -g @oobe-protocol-labs/sap-mcp-server

3. Quick Start

Create or select a profile:

npx sap-mcp-config wizard

Inspect the active profile:

npx sap-mcp-config show
npx sap-mcp-config pubkey
npx sap-mcp-config profiles

Start local stdio MCP:

sap-mcp-server

or from source:

node dist/cli.js

Hosted customers connect their agents to https://mcp.sap.oobeprotocol.ai/mcp, but signing remains user-controlled. Any 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.

4. Local Client Config

For local agents, let SAP MCP follow the active profile manager instead of hard-coding wallet paths or stale RPC overrides:

{
  "mcpServers": {
    "sap": {
      "command": "sap-mcp-server",
      "env": {
        "SAP_MCP_ALLOW_ENV_CONFIG_OVERRIDE": "false",
        "SAP_LOG_LEVEL": "info"
      }
    }
  }
}

See 04. Local Stdio Usage.

5. Remote Server

Remote deployments expose MCP over Streamable HTTP:

node dist/remote/server.js

Production 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.

Remote endpoints:

GET     /health
GET     /.well-known/agent-card.json
GET     /.well-known/sap-mcp-wizard.json
GET     /wizard/install.sh
POST    /mcp
GET     /mcp
DELETE  /mcp

See 05. Remote VPS Deployment and 07. Endpoints And Clients.

6. Monetization

Hosted HTTP deployments can require payment for paid tools/call requests while leaving local stdio and base MCP protocol calls free.

Initial model:

Tier	Examples	Price
Free	tools/list, prompts/list, resources/list, sap_profile_current, base overview	Free
Premium read	sap_list_all_agents, enriched network stats, indexed discovery	$0.007 to $0.01
Builder or batch	complex builders, SNS/domain batch checks, enriched analytics	$0.01 to $0.10
Value action	selected value-linked operations	fixed $0.20 plus optional 0.5%

Enable x402:

SAP_MCP_MONETIZATION_ENABLED=true
SAP_MCP_MONETIZATION_PROVIDER=x402
SAP_MCP_MONETIZATION_PAY_TO=YOUR_SOLANA_USDC_RECIPIENT
SAP_MCP_X402_FACILITATOR_URL=YOUR_PRIVATE_OR_HOSTED_FACILITATOR_URL

Initialize and run the OOBE facilitator:

npx sap-mcp-facilitator init
npx sap-mcp-facilitator start

Generate a pay.sh provider YAML:

npx sap-mcp-pay-sh-spec \
  --out sap-mcp-pay-sh.yml \
  --upstream-url https://mcp.sap.oobeprotocol.ai \
  --network mainnet \
  --recipient YOUR_SOLANA_USDC_RECIPIENT

See 06. Payments, x402, And pay.sh.

7. Commands

pnpm run typecheck
pnpm run lint
pnpm test -- --run
pnpm run build
pnpm run verify:release

Installed binaries:

Command	Purpose
sap-mcp-server	Local stdio MCP server and CLI entry point
sap-mcp-remote	Remote MCP server with bearerless, API key, and JWT modes
sap-mcp-config	Config CLI, profile manager, approval workflow, and wizard
sap-mcp-wizard	TUI configuration wizard
sap-signing-proxy	Local signing proxy
sap-mcp-facilitator	Self-hosted x402 SVM facilitator
sap-mcp-pay-sh-spec	pay.sh provider YAML generator

8. Documentation

Start with 00. Documentation Index.

Document	Purpose
01. Product Overview	Product model, users, public/private repo guidance, and wizard distribution.
02. Architecture And Request Flow	Runtime modules, local flow, remote flow, signing, payments, and trust boundaries.
03. Configuration And Wizard	Profile manager, wizard, wallet isolation, client injection, and config CLI.
04. Local Stdio Usage	Local setup for Claude, Hermes, Codex, OpenClaw, and development agents.
05. Remote VPS Deployment	Hosted deployment, reverse proxy, PM2, and customer onboarding.
06. Payments, x402, And pay.sh	Pricing, x402 gate, pay.sh provider YAML, facilitator signer, and settlement.
07. Endpoints And Clients	HTTP endpoints, headers, smoke tests, and client examples.
08. Security, Policy, And Signing	Key material rules, signer modes, Bento policy, and transaction safety.
09. Tools, Skills, And Agent Guide	Tool families, SDK doc pointers, skills, and agent behavior.
10. Operations, Release, And PM2	Quality gates, PM2, secrets, release packaging, and changelog discipline.
11. Code Quality Audit	Current engineering scorecard, release gates, quality rules, and residual risks.

9. Repository Layout

src/
  adapters/      MCP and Solana adapter helpers
  config/        Runtime config, secure config manager, setup wizard pipeline
  core/          Shared runtime types, errors, logger, constants
  payments/      x402 monetization, facilitator, usage ledger, pay.sh spec
  policy/        Local, Bento, and hybrid policy engines
  remote/        Streamable HTTP MCP server
  resources/     MCP resources
  security/      Private-key, unsafe-action, and permission guards
  server/        MCP server factory and capability registration
  signer/        Local, delegated, and external signer adapters
  tools/         SAP, Solana, AgentKit, SNS, profile, skill, and payment tools
  transports/    stdio and local HTTP transport helpers

10. License

SAP MCP Server is released under the MIT License.

11. Partner Products

Partner / Product	Integration
@bentoguard / Bento Guard	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.