Three.ws Billing MCP Server

Three.ws Billing is an MCP integration. An agent's account economics — plan quotas, metered usage, invoices, receipts, and earnings.

Packages and local setup

The published npm package is @three-ws/billing-mcp, version 0.1.2. Its declared MCP transport is stdio.

The package declares THREE_WS_BASE: Base URL of the three.ws API that serves the billing endpoints. Override only when self-hosting or targeting a preview deployment.; THREE_WS_TIMEOUT_MS: Per-request timeout in milliseconds for the live three.ws API reads.; THREE_WS_SESSION (required): Your three.ws session token (the value of the __Host-sid cookie from a signed-in browser). REQUIRED — it exposes private billing data, so every account-scoped read (get_billing_summary, query_usage, export_billing_history, get_receipt, get_revenue) resolves the calling user from it and returns only your data. Only the public get_fee_info works without it. Treat like a password..

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