Idios MCP Server

Most developer tooling work still happens through a UI a human drives. Idios MCP server moves it into the conversation instead. Private escrow for AI agent work on Beam: verifiable delivery, worker collateral, M of N disputes.

The short version

Pay for AI and compute work privately. Verifiable delivery, escrowed payment, on chain dispute resolution. No public record of amounts or parties.

The tools it exposes

The server publishes 2 tools. What each one is for:

• Roles — The Roles tool exposed by this server
• Prerequisites — All examples use the live Idios contract on Beam Mimblewimble mainnet (cid=41ef8be50f0d727a919b5f5e64f7e66d5ec04442bb4f536f664e38b765e4921f) and a

What it needs from you

• Beam CLI wallet binary, available from the Beam releases page - A copy of idios_app.wasm (downloadable from this repo or built from source, see Build) - A Beam mainnet node to connect to. Run your own, or use a public node like eu-node01.mainnet.beam.mw:8100. All examples use the live Idios contract on Beam Mimblewimble mainnet

Getting it running

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

How it compares

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Idios's toolset — Roles, Prerequisites — is a fair guide to whether it matches your workflow. It is maintained by honeytones; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Things to watch

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.