Docs

Quick start

Run Mesher, call a built-in connector, install your own, and serve MCP.

1. Install

One command per system. The script downloads the release binary for your CPU, checks its SHA-256 against the SHA256SUMS published with the release, and puts mesher on your PATH.

macOS and Linux

x86_64 and arm64; installs to ~/.local/bin.

shell
$ curl -fsSL https://raw.githubusercontent.com/agentrq/mesher/main/scripts/install/install.sh | sh
$ mesher --version

Windows

x86_64, PowerShell; installs to %LOCALAPPDATA%\Programs\mesher and adds it to your user PATH.

PowerShell
PS> irm https://raw.githubusercontent.com/agentrq/mesher/main/scripts/install/install.ps1 | iex
PS> mesher --version
macOS / LinuxWindows
A version other than the latest--version v0.1.0 or MESHER_VERSION-Version v0.1.0 or $env:MESHER_VERSION
Another directory--dir PATH or MESHER_INSTALL_DIR-Dir PATH or $env:MESHER_INSTALL_DIR
Build with cargo instead (needs Rust, Node.js, git)--from-source-FromSource

To pass options through the pipe, use sh -s --: curl -fsSL <url> | sh -s -- --version v0.1.0. With PowerShell, save the script first, then run it with its parameters. Read the scripts before running them.

With Docker

The image is FROM scratch, holds one static binary with the web UI built in, and is published as agentrq/mesher for amd64 and arm64.

shell
$ docker run -d -p 8080:8080 \
    -e MESHER_TOKEN="$(openssl rand -hex 32)" \
    -v mesher-data:/data agentrq/mesher:latest

Open http://localhost:8080/. The first visit shows a setup screen: choose Local machine to keep every default, or Cloud for HTTPS on a public domain.

From source

Or clone and build it yourself. The toolchain and the wasm32-wasip2 target are pinned in rust-toolchain.toml; rustup installs both the first time you run cargo.

shell
$ git clone https://github.com/agentrq/mesher && cd mesher
$ cargo build --release -p mesher
$ export PATH="$PWD/target/release:$PATH"

2. Make your first calls

The built-ins need nothing installed and make no network calls:

shell
$ mesher list
$ mesher math tools
$ mesher math tools equation -b '{"expression":"2*sin(pi/6) + sqrt(16)"}'
$ mesher basic-finance searchTools mortgage, 5
$ mesher time tools now -b '{"timeZone":"Asia/Tokyo"}'

Exit codes: 0 ok, 1 tool or command error, 2 usage error, 3 the connector needs auth. Add --json to print the MCP CallToolResult instead of text.

3. Install a connector

From a local component, which the host checks against the manifest schema before installing:

shell
$ cargo build --release --target wasm32-wasip2 -p mesher-example-httpbin
$ mesher install target/wasm32-wasip2/release/mesher_example_httpbin.wasm
$ printf 'my-key\n' | mesher httpbin tools auth  # the host injects it as X-Api-Key
$ mesher httpbin tools headers

Or a service that already has an MCP server, by its URL. Its sign-in, tools, resources and prompts are discovered:

shell
$ mesher install https://mcp.example.com/mcp --name tracker
$ mesher tracker tools auth
$ mesher tracker tools listIssues -b '{"project":"core"}'

4. Serve MCP

shell
$ mesher serve  # MCP at http://127.0.0.1:8080/mcp, no auth on loopback

Then point your agent at it, for example Claude Code:

shell
$ claude mcp add --transport http mesher http://127.0.0.1:8080/mcp

See Connecting MCP clients for how clients sign in, VS Code, Cursor and other clients.

Where data lives

The data directory is $MESHER_DATA_DIR, else ./_storage (or pass --data-dir). It holds the host's master.key, an optional config.toml, and everything per organization, user and profile. Each profile's credentials sit in their own age-encrypted secrets.age. To share state between servers, use S3 storage.

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