Product

One integration. Every agent connected to memory.

Mesh Router is the connective tissue: a single MCP gateway and native SDKs (TypeScript, Python, Go, .NET, Rust) that route observations in and recall + predictions out. Drop it in once and every agent in your stack shares the same governed memory.

MCP gateway · SDKs (TS · Py · Go · .NET · Rust)

What you get

01

One integration, every agent

Wire the gateway in once; every agent in your stack shares the same governed memory.

02

Three verbs, nothing to learn

observe what happens, recall what matters, predict what's next — that's the whole surface.

03

Routes to the right scope

Every call resolves to the correct project and memory scope automatically.

How it works

How Mesh Router fits in.

  1. STEP 01

    Drop in the gateway

    Add the MCP gateway to Claude Code, Cursor, or Codex — or call the SDK from your own app.

  2. STEP 02

    Point your agents at it

    Observations flow in; recall and predictions flow out, over one API.

  3. STEP 03

    Scope resolves automatically

    The router maps each request to the right project, tenant, and memory scope.

SurfaceMCP gatewaySDKs (TSPyGo.NETRust)

Features

MCP gateway

Standards-based Model Context Protocol — drop into Claude Code, Cursor, or Codex in one command.

Five native SDKs

TypeScript, Python, Go, .NET, and Rust — the same observe/recall/predict surface in your language.

One API, three verbs

observe what happens, recall what matters, predict what's next — nothing else to learn.

Routes to the right scope

Every call resolves to the correct memory scope and project automatically.

Capabilities

Connect

  • MCP gateway for any client
  • TypeScript SDK (more languages coming)
  • One API: observe · recall · predict

Route

  • Per-project / per-tenant routing
  • Scope-aware resolution
  • Governed access

Operate

  • Consistent surface everywhere
  • Provenance end to end
  • Metered usage

FAQ

Questions, answered.

MCP or SDK?+

Both reach the same engine. Use the MCP gateway for drop-in tool integration, or the SDK to embed memory in your own product.

Which languages does the SDK support?+

TypeScript is available today; Python, Go, .NET, and Rust are on the way. The MCP path works with any MCP-capable client now.

Hosted or self-hosted?+

Both are on the roadmap — a hosted gateway and a self-hosted enterprise deployment (MemMesh Edge) that keeps data in your network.

The gateway that wires any agent into the mesh.

The infrastructure layer: an MCP gateway plus SDKs in five languages that connect any agent, tool, or app to MemMesh — one API for observe, recall, and predict.