Openmesha

io.github.ANAMIZEDPublished by GitHub account ANAMIZEDv0.1.0Updated Oct 27, 2026

Open agentic operations mesh MCP: agents, workflows, cost, governance, and x402.

VerifiedSTDIODesktop onlyProductivity & WorkflowFinanceAI & ML

Overview

AI-generated overview

OpenMesha is a local MCP server exposing an agentic operations mesh for agents, workflows, cost budgets, governance and x402 payments.

What you can do
  • The manifest lists no tools, so capabilities come from the README: the MCP server (openmesha-mcp) is one surface of a larger agentic operating system.
  • Manage agents as OS-like processes with budgets and least-privilege controls.
  • Run and trigger multi-agent workflows through MCP, the REST API or the CLI.
  • Track cost as a first-class resource alongside governance and fail-closed controls.
  • Reach the same system through a web control plane, REST API, SDK and CLI.
When to use it
Worth considering if you want an assistant to drive a self-hosted agentic operations stack — spawning agents, running multi-agent workflows and watching budgets and governance — rather than a single-purpose tool. Most users will not need it unless they already run or intend to deploy the OpenMesha system.
Requirements
Runs as a local stdio process on the desktop; no packages, environment variables or headers are declared in the manifest. The README's quick start uses Docker Compose and a verification script, with the API on localhost:8080, so a Docker-capable machine and the repository source are implied.
Before you install
The README asks for payments: a $99 support tier, a $0.75 cycle, and non-custodial USDC addresses on Base, Ethereum and Solana, so treat any transfer as a real spend. The system is described as controlling agents, budgets and settlement, so expect actions that change state. No credentials are declared, but verify what the local process can reach before running it.

Installation

In SourceWeft

  1. Open Openmesha in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

OpenMesha (OM)

[CI] [License] [Python 3.11+] [MCP] [SDK] [CLI] [API] [x402]

“Autonomous Local Economic System”

🚀 Live Demo

[Live Demo]

Interactive 14-chapter systems briefing (fully self-contained single file) — kernel, agents, economy, security, quantum, x402, HOTL, and more.

→ Open the live interactive demo


OpenMesha is a production-oriented agentic operating system: Super kernel (Thompson router, bitemporal memory, QAOA/VQE, AgentFence, x402, HOTL, PQC) delivered as a self-contained web control plane, plus a Python control plane with OS-like primitives — agents as processes, budgets, multi-agent workflows, MCP, SDK, and CLI.

A senior engineer who has never seen this repository can, using only the source and this README.md:

  1. Deploy the entire system (single command)
  2. Exercise every major feature
  3. Verify end-to-end correctness via automated checks

Support Agentic OS Kernels ($99) · Agentic OS Cycle ($0.75) · Public Goods Support

Non-custodial USDC (preferred for agents)

NetworkAddressExplorer
Base0xD3d0E9eDAe3Ac7bb199a8EAA761BdA423b878438basescan
Ethereum0xD3d0E9eDAe3Ac7bb199a8EAA761BdA423b878438etherscan
SolanaETQwWf19axArsY493UfC6bxe2BmEzmzvCb58PPnC38Asolscan

Related: rui · server-os · LRSI · OpenGOS

Surfaces

SurfaceEntry
Live Demo (GitHub Pages)OpenMesha-Briefing-SingleFile.html
Web control planeweb/openmesha.html
REST APIopenmesha-api / python -c "from openmesha.main import run; run()"
CLIopenmesha status / openmesha agents ... / openmesha workflow
MCP Serveropenmesha-mcp
SDKfrom openmesha.sdk import OpenMeshaClient
Multi-agent workflowsPOST /v1/workflows · MCP · CLI · skills/multi-agent-workflow/
Skillsskills/*/SKILL.md
CI.github/workflows/ci.yml
AGENTS.mdCoding-agent contract at repo root
WIRE production pathdocs/WIRE.md — full cloud/self-hosted path: architecture, om-ctl API, stack, Foundry economics, settlement, P0–P4 checklists

Quick Start

bash
docker compose up --buildbash scripts/verify.sh

Design principles

  1. Least privilege by construction
  2. Cost is a first-class resource
  3. Fail closed (AgentFence + HOTL)
  4. Honest offline simulation
  5. Deployable with zero tribal knowledge

License

Apache-2.0

Source: README.md at commit bbe9e32

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.