Three.ws Agent Payments MCP Server

Three.ws Agent Payments is an MCP integration. Governed x402 payment sessions: pay any endpoint with budget, allowlist & per-tx caps, no key.

Packages and local setup

The published npm package is @three-ws/agentcore-payments-mcp, version 0.1.4. Its declared MCP transport is stdio.

The package declares THREE_WS_SESSION: Your three.ws session token (value of the _Host-sid cookie from a signed-in browser). Required for account management operations: create_payment_session, list_payment_sessions, check_payment_session, cancel_payment_session.; PAYMENT_SESSION_TOKEN: A payment session bearer token (starts with 'pss') from create_payment_session. Used by the agent for pay_with_session calls when no inline token is passed. Treat like a spending card — it authorizes payments up to the session's budget.; THREE_WS_BASE: Base URL of the three.ws API. Override only when self-hosting or targeting a preview deployment.; THREE_WS_TIMEOUT_MS: Per-request HTTP timeout in milliseconds. x402 payments involve on-chain settlement so this should be generous (default: 30000)..

Before connecting

Check the maintainer’s instructions for account access, authentication and the supported client configuration. Once connected, inspect the tools your client receives and try a small task that matches the server’s stated purpose. The registry description does not include a verified, complete tool list.

Project and source

View the publisher’s registry entry · Project repository · Project website. This profile uses version 0.1.4 from the registry. Registration identifies the publisher namespace; it does not establish that this is a first-party integration for every service it connects.

Browse related payments & commerce MCP servers for tools that cover the same kind of work.