MCP Passthrough connects an MCP client to an eIOU node. The node runs model requests through providers configured by its operator or through participating nodes discovered via its contacts. The plugin records the client’s usage and charges it in the agreed eIOU currency.
Your client connects to your serving node with a client key. The serving node manages its provider connections. A provider may run its own model or use an online model API; nodes hosted by us use remote inference and do not run local models or Ollama sidecars.
For a first setup, follow the three guides in order. If the plugin is already running, use the reference to find a command, panel control, or API contract.
1. Node & access
Install the plugin, arrange the billing identity, issue a client key, and fund it.
2. Providers
Connect participating eIOU nodes or an online model API, set limits, and check readiness.
3. Clients & first call
Set up Cursor, Claude Desktop, or Claude Code, test a call, and inspect its recorded usage.
Reference
Look up CLI commands, GUI controls, API contracts, and the plugin’s architecture.
Understand the roles
- Client user: connects their application and makes model calls using the serving node’s key.
- Node operator: configures access, providers, prices, spending limits, and client billing.
- Provider operator: offers inference and agrees admission, prices, and funding with the buying node.
Where examples use letters, the billing wallet is A, the serving node is B, and an inference-provider node is C. They identify distinct roles in the example.
Client access in this release: default pilot mode requires a key bound to a distinct accepted billing contact. Owning one node does not create an owner key. Review the billing-contact requirement before setup.
The alpha pilot offers help testing this setup after manual acceptance. Applying does not automatically provision a node, issue a key, or fund a provider.