Docs
Introduction
What Mesher is, the handful of ideas it is built on, and where to go next.
Mesher is a small Rust host that runs WebAssembly components as MCP servers and as CLI apps at the same time. You install connectors, such as Gmail or a remote MCP server, and your agents reach all of them through one MCP tool, callTool.
gmail.searchTools 'unread' 10
gmail.tools sendEmail help
gmail.tools sendEmail -b '{"to":"ada@example.com","subject":"Hi","text":"Hello"}'
gmail.tools authThe same commands run from a shell as mesher gmail tools sendEmail -b …. MCP and the CLI share one parser and one dispatcher, so a command behaves the same in both.
Concepts
- Connector
- A
wasm32-wasip2component with itsmanifest.jsonembedded in it, or a remote MCP server installed by its URL. Connectors come from a local.wasmfile, the GitHub catalog, or a URL. - Host
- The
mesherbinary. It runs each call in a fresh sandbox, makes every HTTP request for the connector, checks it against an allowlist and adds your credentials itself. callTool- The single MCP tool. It takes a command line, so an agent finds, reads and calls tools the way you would in a shell.
- Profile
- A named set of connectors, each signed in to one account, such as
workandpersonal. An MCP app is let into one profile and sees only what it exposes. - Built-ins
- Connectors compiled into the binary:
manage,cron,workflows,wasmrs,time,math,basic-finance,hash,stringsandslices.
Where to next
Quick start
Run Mesher with Docker or from source and make your first calls.
The callTool language
Every command, flag and rule, for MCP and the CLI.
Connecting MCP clients
Claude Code, VS Code, Cursor and any OAuth client.
Profiles & TOON
Keep accounts apart and cut tokens with TOON output.
Schedules & workflows
Cron jobs and model-free tool chains.
Security model
How untrusted connectors are contained.
Building a connector? Read the authoring guide and the manifest reference.
Last updated November 21, 2026 · This page as Markdown · Full reference on GitHub