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.

callTool
gmail.searchTools 'unread' 10
gmail.tools sendEmail help
gmail.tools sendEmail -b '{"to":"ada@example.com","subject":"Hi","text":"Hello"}'
gmail.tools auth

The 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-wasip2 component with its manifest.json embedded in it, or a remote MCP server installed by its URL. Connectors come from a local .wasm file, the GitHub catalog, or a URL.
Host
The mesher binary. 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 work and personal. 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, strings and slices.

Where to next

Building a connector? Read the authoring guide and the manifest reference.

Last updated November 21, 2026 · This page as Markdown · Full reference on GitHub