How do I install @stableops/agent Payments?

Copy the stdio config for Cursor, Claude Desktop, Claude Code, or VS Code on this page. It uses the publisher's install, not a PlugMCP proxy.

Does @stableops/agent Payments need an API key?

No required environment variable is listed on this record.

What transport does @stableops/agent Payments use?

@stableops/agent Payments runs locally over stdio.

When was @stableops/agent Payments last checked?

Last checked 2026-11-11. Stdio MCP server for configuring and running StableOps Agent Payments.

@stableops/agent Payments MCP 服务器

接入你的智能体

添加此服务器

The publisher's own command. Not a PlugMCP endpoint.

Add to Cursor Add to VS Code 在 PlugMCP 上运行

用我们的密钥与日志托管一份副本。

Local command

npx -y @stableops/[email protected]

Claude Code has no install link for a local command. Copy the command below and run it in a terminal.

shClaude Code

1claude mcp add stableops-agent-payments-mcp-server -- npx -y @stableops/agent-payments-mcp-server@0.3.1

Run in a terminal.

jsonClaude Desktop

1{2  "mcpServers": {3    "stableops-agent-payments-mcp-server": {4      "command": "npx",5      "args": [6        "-y",7        "@stableops/[email protected]"8      ]9    }10  }11}

claude_desktop_config.json

Local · npmPublisher installStep-by-step: add this in Claude

Remote URL or a command on your machine? How the two installs differ

在 PlugMCP 上运行

用我们的密钥与日志托管一份副本。

这是你新建的服务器，不是此条目的官方端点。若要用发布方的 URL 与凭证，请使用上方安装面板。

启动

Server facts

Local

Transport: stdio
Version: 0.3.1
Last checked

Tools

No tool list yet. Remote servers get one after the first health check.

FAQ

Questions

StableOps Agent Payments MCP Server

A stdio Model Context Protocol (MCP) server that lets agents configure and run StableOps Agent Payments while private keys, seed phrases, KMS credentials, and approval authority remain user-controlled.

Install and run

Node.js 20 or later is required.

Provide only the management key during setup:

STABLEOPS_API_KEY=sk_sandbox_... \ STABLEOPS_AP_ENABLE_MANAGEMENT_WRITES=true \ STABLEOPS_AGENT_KEY_OUTPUT_FILE=/protected/absolute/path/stableops-agent-key \ npx -y -p @stableops/agent-payments-mcp-server stableops-agent-payments-mcp

Management mode is read-only by default. Mutating tools are registered only with STABLEOPS_AP_ENABLE_MANAGEMENT_WRITES=true; the management process never exposes open-world discovery or payment execution. The one-time Agent Key secret is never returned to the model. The server reserves the 0600 destination before issuance and automatically revokes a newly issued key if storage fails.

The wallet-pairing tool returns only the exact message the user must sign. No tool accepts a private key, seed phrase, or KMS credential. The user signs in their own wallet and returns only the signature.

For daily runtime use, remove the management key and use a restricted Agent Key plus the user-operated signer sidecar:

STABLEOPS_AGENT_KEY=ak_sandbox_... \ STABLEOPS_SIDECAR_URL=http://127.0.0.1:8789 \ STABLEOPS_SIDECAR_TOKEN=... \ npx -y -p @stableops/agent-payments-mcp-server stableops-agent-payments-mcp

Management and runtime modes are mutually exclusive. The server refuses to start when both STABLEOPS_API_KEY and STABLEOPS_AGENT_KEY are set. Runtime mode only exposes discovery, budget, preview, controlled purchase, and payment-reconciliation tools; it cannot change policy or approve its own payment.

Security model

The server never accepts or stores wallet private keys, seed phrases, or KMS credentials.

The user must sign wallet-ownership proofs outside the server.

Runtime payment can only call the user-operated constrained signer sidecar, never an arbitrary signing endpoint.

Unknown origins, unknown recipients, and above-threshold payments require human approval in StableOps.

Every new purchase requires a stable idempotency_key; uncertain settlement must reconcile the original intent.

Every purchase must use a preview_token bound to the exact URL, maximum quote, and audit context; the purchase tool accepts no replacement URL.

Preview tokens are process-local. After an MCP restart, preview the original exact URL again and resume with the new token; the API verifies the full URL hash stored on the intent.

Responses over 256 KiB are available as short-lived MCP resources; all inline summaries are marked as untrusted external content.

Documentation

License

Apache-2.0