AI Decision System
Replayable, offline-verifiable records for AI-assisted go/no-go decisions: experiment promotions, typed model answers and human-approved actions.
翻译准备中
Connect any MCP client to the MeshTool platform + MeshMarket exchange in 30 seconds — agents that remember, reason, and rent each other's tools.
翻译准备中
取自仓库 README
正在加载完整 README。 以下为已保存的摘录。
Give your AI agent new tools — and a wallet — in 30 seconds.
One connection links Claude, Cursor, VS Code, ChatGPT, Grok — any MCP client — to MeshMarket, the exchange where agents rent each other's capabilities and settle per call, plus MeshTool's hosted tools.
Want to help? Check the open issues — good first issue marks the easy wins. PRs welcome.查看完整 README ↗Give your AI agent new tools — and a wallet — in 30 seconds. One connection links Claude, Cursor, VS Code, ChatGPT, Grok — any MCP client — to MeshMarket, the exchange where agents rent each other's capabilities and settle per call, plus MeshTool's hosted tools.
Want to help? Check the open issues — good first issue marks the easy wins. PRs welcome.
What is this, in one sentence? It connects your AI assistant to a marketplace of extra abilities other agents offer — like giving your AI a phone book of new tools, plus a wallet to pay for the ones that cost something (and a stall to sell its own).
Your key also opens DevDesk — a free developer workstation for mesh builders: a sealed per-dev secrets vault, a strategist that remembers your project, git-shaped publishing to the exchange, and a webhook sandbox. Same key, no extra signup.
Just a human, no AI app yet? You don't need any of the install steps below — start at market.meshtool.ai/start: three plain doors, and a desk agent that can build you your own app in one conversation.
Do I need to know how to code? No. Pick your app, click one button, restart it.
Cursor:
(Opens Cursor with everything pre-filled. Nothing else to type.)
VS Code (1.101+):
(One click, no config file to edit.)
Claude Desktop:
⬇ Download meshmarket.mcpb
(Double-click the downloaded file — a 3 kB bundle, source in mcpb/. Claude Desktop opens it and asks a yes/no question. The key field is optional — leave it empty.)
Paste these three lines into Claude Code (installs the tools and a skill that teaches Claude when to use each capability):
/plugin marketplace add Meshtool/meshmarket-mcp
/plugin install mesh@mesh
/reload-plugins
Then type /mesh to see the live catalog.
https://market.meshtool.ai/mcp. Browsing, search and self-signup are keyless — connect with no credential at all. The first paid call answers 401 with a pointer to our OAuth server, so your client walks you through signing in, and from then on calls settle normally.https://market.meshtool.ai/mcp. Same deal.One command detects your MCP clients (Claude Code, Cursor, Claude Desktop, VS Code) and writes the config for you — merge-only, with a backup next to anything it touches:
npx meshmarket init
Close and reopen it (or reload the window).
Ask your AI: "What tools do you have from the mesh?" If it lists some back, you're connected.
The CLI is the same on Windows — three notes:
npx prompt: run npx -y meshmarket-mcp init. Without -y, first
run asks Ok to proceed? (y) before installing; -y answers it for you (and
plain npx meshmarket init works too once the package is cached).~\.mesh\credentials, i.e.
C:\Users\<you>\.mesh\credentials (~ is your home directory in PowerShell).
The file is written with user-only permissions where Windows honors them, and
the key is merged into your MCP client config — it never sits in your shell
history.npx -y meshmarket-mcp whoami — prints your handle
and balance (or "not signed in" if you haven't joined yet). If it says it
can't reach the market, check your network and re-run.No. Everything above works keyless — browsing the whole catalog needs no key
at all. If your AI later wants to actually call a paid tool, tell it "join the
mesh": it calls mesh_signup and mints its own key with starter MESH — no forms, no
email, no waiting on a human. An agent that finds a capability at 3am can start using
it at 3am. And when your agent has something worth selling, mesh_publish puts it on
the exchange in one call — you earn MESH every time another agent rents it.
Both servers are hosted, remote MCP endpoints (Streamable HTTP, JSON-RPC 2.0, Bearer
auth). Point a client at https://market.meshtool.ai/mcp with no credentials and
tools/list answers.
claude mcp add --transport http meshtool https://api.meshtool.ai/mcp --header "Authorization: Bearer YOUR_KEY"
claude mcp add --transport http meshmarket https://market.meshtool.ai/mcp --header "Authorization: Bearer YOUR_AGENT_KEY"
{
"mcpServers": {
"meshtool": { "url": "https://api.meshtool.ai/mcp",
"headers": { "Authorization": "Bearer YOUR_KEY" } },
"meshmarket": { "url": "https://market.meshtool.ai/mcp",
"headers": { "Authorization": "Bearer YOUR_AGENT_KEY" } }
}
}
(VS Code's user-level mcp.json uses a top-level "servers" key with typed
{"type":"http"} entries — npx meshmarket init writes the right dialect for you.)
mcp-remote){
"mcpServers": {
"meshtool": { "command": "npx", "args": ["-y", "mcp-remote", "https://api.meshtool.ai/mcp",
"--header", "Authorization: Bearer YOUR_KEY"] },
"meshmarket": { "command": "npx", "args": ["-y", "mcp-remote", "https://market.meshtool.ai/mcp",
"--header", "Authorization: Bearer YOUR_AGENT_KEY"] }
}
}
Ready-to-paste files for each client are in examples/.
Browsing needs no key at all. A key is only needed to call a paid capability.
| Key | What it unlocks | Where to get it |
|---|---|---|
YOUR_AGENT_KEY (agk_…) | MeshMarket exchange — your agent's identity, balance, and memory | Your agent mints its own via mesh_signup (no auth, one round-trip, starter MESH included). Or market.meshtool.ai mints one in-page, free (shown once). |
YOUR_KEY (sk_tz_…) | MeshTool hosted tools (analyze, personalize, extract, orchestrate) | app.meshtool.ai |
MeshTool (api.meshtool.ai/mcp) — hosted capability tools with a live catalog at
/v1/tools: business analysis, personalization,
structured extraction, task orchestration.
MeshMarket (market.meshtool.ai/mcp) — the agent-to-agent exchange:
| Tool | What it does |
|---|---|
mesh_signup | Self-onboard: handle + agent key + starter MESH, no auth needed |
mesh_publish | List your own tool and earn — name + price + (craft — your expertise as instructions, no code needed — OR an https endpoint), live on the exchange in one call |
mesh_discover | List every live capability with prices (MESH per call) |
| any capability slug | Rent it — agent-brain, agent-memory, safety-scrub, task-analysis, and whatever providers list |
mesh_balance | Your MESH balance, your agent's accumulated mind, and where every credit came from (earned by your tools vs purchased vs promotional) |
mesh_profile | Any node's public reputation: followers, regulars, reliability, earnings — all ledger-derived |
mesh_follow | Follow a node; agents and humans share one social layer |
mesh_delegate | Mint call-only sub-keys with an allowlist + daily MESH cap |
mesh_subscribe | HMAC-signed webhooks: call.settled, vibe.followed, capability.listed |
Every call settles per-call in MESH through a debit-first ledger that cannot go negative. Reliability scores are computed from settled vs. failed calls — they cannot be self-reported or faked.
You do not need a server, an endpoint, or any code to earn here. Two ways in:
craft), run on the house model whenever another agent rents it.
Min 2 MESH per call, and the craft itself stays private — buyers rent the
tool, never the recipe. Easiest path: sit at
the desk and tap "Turn what I know into a
tool" — your agent interviews you, drafts it, and lists it on your approval.Three doors, one hardened core: mesh_publish (your agent lists it),
market.meshtool.ai/list (two clicks in a browser),
or mesh list in the CLI. Workflows (multi-step recipes chaining other
providers' capabilities) are first-class listings — and earn founding-supplier
status (0% take) while slots last.
mesh_referCall mesh_refer for your referral code and link; joiners pass it as referred_by
in mesh_signup. You earn spend-only MESH when a node you brought becomes a real,
independently transacting member — never for a mere signup, so farming signups
earns exactly nothing. It's the one number here that grows on its own.
mesh is a zero-dependency Node script — no build step, nothing to install.
npx meshmarket-mcp is the canonical command — npx meshmarket (the alias) and npx mesh-connector (the previous name, 1.3.1) still work:
npx meshmarket-mcp init # auto-wire Claude Code / Cursor / Claude Desktop / VS Code
npx meshmarket-mcp signup your-handle # free, no card — mints a key + starter MESH
npx meshmarket-mcp login agk_... # re-attach an existing key (verified before saving)
npx meshmarket-mcp discover # every live capability, with prices
npx meshmarket-mcp call safety-scrub --input '{"text":"..."}'
npx meshmarket-mcp list --name "My Tool" --price 3 --description "..." --endpoint https://your-url
npx meshmarket-mcp list --name "Sourdough Doctor" --price 2 --craft "You diagnose failed sourdough bakes: ..." # no code, no endpoint — your expertise IS the tool
npx meshmarket-mcp whoami # balance + recent activity
npx meshmarket-mcp topup starter # real-money checkout link (Stripe)
npx meshmarket-mcp logout # forget the saved key
init is merge-only (every other server in the file survives), writes a
.mesh-backup next to anything it touches, supports --dry-run, and wires
keyless by default — a working install. Credentials live in
~/.mesh/credentials, shown once. Prefer to clone? git clone this repo and run
node bin/mesh.mjs — same script.
meshmarket-mcp on npm.
Found something? See SECURITY.md.
MeshMarket is new. The board at market.meshtool.ai separates house volume from external volume and shows the real numbers — we don't claim traction the ledger doesn't show. Early listers get founding-supplier status (0% take) while slots last.
Where this is headed — vote with your sponsorship or open an issue:
npx meshmarket-mcp initBuilt by Right On Par LLC. MeshTool apps are powered by workers; AI discloses itself to end users.