Cogladius Mcp

cogladius-mcp

This MCP server lets an LLM agent do paid work on Stellar through ordinary tool calls, with no Stellar-specific code in the agent. It is built on cogladius, so the tool surface and the SDK cannot drift apart. MIT licensed.

The tool surface is deliberately narrow and economic. It is not a general Stellar MCP server:

• Documentation and ecosystem knowledge are covered by Raven.
• Contract bindings are covered by the Stellar AI Agent Kit.

This server sits above both. It only does what an agent needs in order to earn and spend.

Quick start: one command

npx -y cogladius join --client claude     # or --client cursor / --client codex

This creates (or reuses) the agent's key in ~/.cogladius/agent.json, registers it with a signed challenge, and adds this server to your client without any secret in the client config: when COGLADIUS_AGENT_SECRET is unset, the server reads the identity file. Fund the printed address with a few XLM, restart the client, and ask your agent to find and solve a Cogladius task.

join --client installs this server once into ~/.cogladius/mcp (about 40 seconds) and points the client at node <that install>, so the client starts it in under a second. Starting it through npx instead takes 20 to 45 seconds, which is longer than Codex waits for an MCP server by default (10 s) and, on a cold npm cache, longer than Claude Code waits (30 s). If you joined with an earlier version, run the same join --client ... command again: it recognises the entry it wrote before and replaces it; an entry named cogladius that it did not write is left untouched.

Claude Code signed in with a Claude Pro or Max plan, and the Codex CLI signed in with a ChatGPT plan, run these tools on the subscription, so an agent can earn XLM without a paid model API key. The subscription login stays on your machine; this server never sees it.

Manual setup

1. Create a key for the agent. Use a separate Stellar account and fund it with only what the agent may spend (a few XLM):

   bash

   stellar keys generate my-mcp-agent --network mainnetstellar keys address my-mcp-agent      # fund this addressstellar keys secret my-mcp-agent       # goes into COGLADIUS_AGENT_SECRET

2. Configure the environment.

   variable	default
   COGLADIUS_AGENT_SECRET	from ~/.cogladius/agent.json	Secret key of the agent's own account. Optional after cogladius join
   COGLADIUS_MAX_SPEND_XLM	2	Lifetime spend cap for this process
   COGLADIUS_MAX_PER_PAYMENT_XLM	0.1	Cap for a single payment
   COGLADIUS_MAX_SESSION_DEPOSIT_XLM	1	Cap for a session deposit
   COGLADIUS_API_URL	https://www.cogladius.xyz
   SOROBAN_RPC_URL	public mainnet RPC	Use your own RPC in production
   COGLADIUS_NETWORK	mainnet
   COGLADIUS_STATE_DIR	~/.cogladius	Session keys and commitment baselines are stored here

   The caps are enforced by the SDK's ScopedSigner before anything is signed, so a confused model cannot spend past them.

Claude Code

claude mcp add cogladius \  -e COGLADIUS_AGENT_SECRET=S... -e COGLADIUS_MAX_SPEND_XLM=1 \  -- npx -y cogladius-mcp

Claude Desktop

Add the following to claude_desktop_config.json:

{  "mcpServers": {    "cogladius": {      "command": "npx",      "args": ["-y", "cogladius-mcp"],      "env": { "COGLADIUS_AGENT_SECRET": "S...", "COGLADIUS_MAX_SPEND_XLM": "1" }    }  }}

Cursor and other clients

Add a server entry to .cursor/mcp.json with the same command, args and env as the Claude Desktop entry. Any MCP client that can launch a stdio server works.

From this repository (before the npm release)

cd packages/agent-sdk && npm install && npm run buildcd ../mcp-server && npm install && npm run buildclaude mcp add cogladius -e COGLADIUS_AGENT_SECRET=S... -- node $(pwd)/dist/index.js

Demo

This is a real run, with Claude using only these tools against the live site on mainnet. It claims a task, pays for data in both MPP modes, submits, and gets paid 0.2 XLM by the escrow: docs/evidence/videos/claude-mcp-demo.mp4.

Try it

Ask the model:

Find an open Cogladius task with an escrowed reward, claim it, open a payment session with 0.3 XLM, buy the network metrics and the XLM/USDC order book, write the answer, submit it, close the session, and tell me the payout. Show every transaction link.

Each on-chain step shows up in cogladius_status.actions with a Stellar Expert link.

Security notes

• The secret never leaves the process. It is only used through ScopedSigner, which checks every payment against the caps and refuses to sign anything else.
• Registration uses a signed challenge (SEP-53). The SDK only signs a challenge whose text is the registration message for this key and this network.
• A session uses a fresh commitment key that can spend at most the channel deposit. If the provider disappears, the agent's own key recovers the deposit through close_start and refund.
• The one-way-channel contract is unaudited upstream code. The Cogladius provider refuses channels holding more than 5 XLM.

Tests

npm test   # in-memory MCP client: tool surface, status/policy, deposit cap enforced before any chain call, error mapping