Download
All plugins
Pre-releasev0.29.3

eIOU MCP Passthrough

Connect your MCP client to your own eIOU node to find and pay for AI inference through your contacts, or offer models to other participants.

Download v0.29.3 (.zip)Plugin documentationView on GitLabExplore the alpha pilot

Upload-ready package from GitLab release v0.29.3. Browse all releases or inspect the source repository.

Version
0.29.3
Requires
eiou-docker v0.1.21-alpha
License
Apache-2.0
Transport
Streamable HTTP

Overview

Use AI inference through your own node

Connect your MCP client to an eIOU node you control. With automatic routing enabled, your node can discover model providers through your contacts, arrange credit with a reachable provider, and return the answer to your client. You do not need to run a model or own a GPU to buy inference. You can also offer local models or hosted API access to other participants and set your own prices.

01

Connect your client

Use one customer API key from your own node; your node manages the credentials needed for network providers.

02

Find a provider

Enable automatic routing to use eligible model offers discovered through your contacts, within your spending limits.

03

Pay in eIOU credit

Use credit accepted by the participants along a route. Availability depends on their limits, terms, and willingness to extend credit.

04

Offer inference too

Optionally connect local models or hosted APIs, set prices, and issue customer keys to sell inference.

Before you begin

Requirements

  • An eIOU node you control, compatible with eiou-docker v0.1.21-alpha. This can be self-hosted or a hosted node for which you have administrative access.
  • Each node needs its own installation of the MCP passthrough plugin. Nodes we host use remote inference providers or online model APIs; our hosted servers do not support local models or Ollama sidecars.
  • To buy inference: eligible provider offers reachable through your contacts and sufficient accepted credit. A provider node, hosted model API key, and GPU are not required on your own node.
  • For the HTTPS client recipes: a reachable node hostname and a TLS certificate your client trusts. The basic Docker setup uses a self-signed certificate until you configure trusted HTTPS.
  • A client key admitted by the node. Default pilot mode requires a key bound to an accepted contact; owning the node does not automatically create a self-use key. Coordinate the key binding and credit arrangement during pilot setup.
  • Approval for the wallet, contact-directory, host-resource, and outbound-payment permissions requested during enablement.
  • To offer inference: a local model service or hosted provider API account. GPU capacity is relevant when you choose to run local models.

Installation

Download and upload the plugin

Pre-release

Release v0.29.3 is published as a pre-release for eiou-docker v0.1.21-alpha. Its ZIP is ready to upload directly to eIOU; you do not need to clone or extract the repository, and no local build is required. Review pre-release software before production use.

  1. 1

    Download the release ZIP

    Download mcp-passthrough-v0.29.3.zip and its SHA-256 checksum. Follow the verification instructions below before upload. Keep the archive intact; eIOU validates and extracts it during upload.

  2. 2

    Upload and enable

    In your eIOU node, open Plugins, choose Upload .zip, select mcp-passthrough-v0.29.3.zip, enable the plugin, approve its requested permissions, and turn on its Public routes toggle. Public plugin routes are permitted by default; until this plugin's toggle is on, the customer MCP route returns 404.

Verify your download

Check the checksum and publisher signature

Save the release ZIP andchecksum file in the same folder. The expected SHA-256 for mcp-passthrough-v0.29.3.zip is:

1d97b13b467968efb26f188e2c085574deb68faed62aa5aefcb87eec44c0cb4c

Run the command for your operating system from that folder. Linux and macOS must report OK; stop if the checksum does not match.

Linux

sha256sum -c mcp-passthrough-v0.29.3.zip.sha256

macOS

shasum -a 256 -c mcp-passthrough-v0.29.3.zip.sha256

Windows PowerShell

$expected = (Get-Content .\mcp-passthrough-v0.29.3.zip.sha256 -Raw).Trim().Split()[0]
$actual = (Get-FileHash .\mcp-passthrough-v0.29.3.zip -Algorithm SHA256).Hash
if ($actual -ne $expected) { throw "Checksum mismatch: do not install" }
"Checksum OK"

A matching checksum confirms that the ZIP matches the published bytes. It does not independently establish who published them if the ZIP and checksum source are both compromised. The ZIP also contains an Ed25519 publisher signature in plugin.sig, which eIOU checks against its trusted publisher keys during installation. Do not bypass a failed signature check.

Verify the publisher signature before uploading

On Linux, macOS, or Windows with WSL, use Bash 4 or newer, Git, Python 3, and PHP with the sodium extension. On macOS, install a current Bash first; the system Bash 3 cannot run this verifier. From your download folder, run the matching release's verification script. This fetches the host verifier and trusted keys pinned by that release and checks both the signature and rejection of a modified copy; it does not change your original ZIP.

git clone --depth 1 --branch v0.29.3 \
  https://gitlab.com/eiou-org/eiou-plugin-mcp-passthrough.git eiou-mcp-verification
bash eiou-mcp-verification/scripts/verify-release-signature.sh \
  "$PWD/mcp-passthrough-v0.29.3.zip"

Expect a signature result of ok, a tamper-test result ofbad_signature, and the final message confirming verification. The trust decision still depends on obtaining the repository and its pinned publisher keys from a source you trust. See therelease verification script.

Downloads

Available releases

The upload-ready release below is used by the main download button. Browse the GitLab release history for source tags and release notes.

View the complete release history on GitLab. GitLab may ask you to sign in when repository access is restricted.

Configuration

Choose how your node gets inference

To buy through your contacts, open the plugin's Networktab, enable Automatic routing, and set your spending limits. Routing is off by default. Your node needs eligible provider offers and a usable credit route; enabling it does not guarantee capacity. Review eligible offers and use Warm the best sellers nowto prepare their credentials. Routed funding may take time to arrive; a provider must be ready before it can serve a call. Follow the client-specific connection recipesonce pilot setup has established a valid client key on your node. The client key needs sufficient prepaid balance or available credit extended to its bound contact. This allowance is separate from your node's credit route for funding the selected provider.

To offer your own inference, use the MCP Passthrough panel to add a provider, fetch its models, set pricing, and select the active model. On infrastructure you operate, you can run a local Ollama sidecar and use the CLI setup below. This local-model example does not apply to nodes we host:

docker exec <eiou-container> eiou mcp-passthrough provider configure \
  ollama --preset=ollama --endpoint=http://ollama:11434

docker exec <eiou-container> eiou mcp-passthrough provider use \
  ollama qwen2.5:0.5b

Hosted-provider checks and inference may create real charges on the upstream account. Confirm the rate card and markup before issuing customer keys.

Customer connection

Add the MCP endpoint to a client

In default pilot mode, issue customer keys in the plugin panel against accepted contacts. A key can spend its prepaid balance or available credit extended to that contact. Node ownership alone does not bypass this admission requirement, and a node cannot add itself as a contact;coordinate your client setup with pilot support. Once the key is ready, Streamable HTTP clients use the node's reachable, trusted HTTPS URL:

https://<your-eiou-host>/p/mcp-passthrough/mcp
Authorization: Bearer mcp_<CUSTOMER_API_KEY>

The server exposes billed chat completion alongside model listing, recent usage, balance checks, and top-up instructions. Follow the separateClaude Desktop, Cursor, and Claude Code recipesfor authentication and configuration locations.

Operations

Security and usage notes

  • The plugin runs in a sandboxed per-plugin PHP-FPM process and uses bearer-authenticated public routes.
  • Requests are intentionally limited to 1 MiB, below the host request ceiling, and local providers serialize work per provider with retryable busy feedback.
  • Use HTTPS for non-onion public endpoints and restrict each key's allowed browser origins.
  • Keep the eIOU host and plugin source updated, and validate provider pricing before deployment.