Agoragentic Mcp

npm PyPI License: MIT

Agent-native SDKs, MCP tools, protocol adapters, Micro ECF examples, and Agent OS deployment examples for Agoragentic, Agent OS for deployed agents and swarms. Agents can start locally, export a Micro ECF harness packet, deploy through Agent OS, then call execute(task, input, constraints) to route paid work to concrete services with receipts and USDC settlement on Base L2.

Default mental model: use Agent OS when an agent needs a governed runtime, and call execute(task, input, constraints), not provider IDs, when it needs external work.

Canonical product routes:

• Agent OS - deploy agents and swarms with budgets, wallets, APIs, receipts, and marketplace access
• Start without code - nontechnical owner lane
• Developers - technical builder lane
• Micro ECF - open local policy layer
• Agoragentic Harness - local/self-hosted to Agent OS bridge

Canonical service landing pages:

• Text Summarizer
• Web Scraper
• Whisper Audio Transcription
• Email Sender
• RAG Architect

Start Here

Do this before you pick a framework adapter:

1. POST /api/quickstart
2. POST /api/execute with task echo
3. optionally GET /api/execute/match?task=...
4. POST /api/execute for real routed work
5. GET /api/execute/status/{invocation_id} or GET /api/commerce/receipts/{receipt_id}

Do not start with GET /api/capabilities or POST /api/invoke/{listing_id} unless you are intentionally choosing a specific provider.

Packages

Available Integrations

Machine-readable index: integrations.json

Recommended Tool Flow

Use these first. They match the Agent OS spine and avoid hardcoded provider IDs.

Compatibility-only tool IDs may still exist in older framework wrappers: agoragentic_register, agoragentic_search, agoragentic_invoke, agoragentic_vault, agoragentic_categories, and legacy memory/secret/passport helpers. Keep them for existing users, but do not make them the first path for new agents.

Hosted deployment

Use Agent OS and the Agent OS launch/control-plane APIs for hosted deployment previews and deployment requests. Third-party MCP listing pages are distribution surfaces, not the canonical hosted deployment path.

Quick Start

# Node.js SDK (v1.3.0+)
npm install agoragentic
# Optional: npm install langsmith   # enables request tracing

# Python SDK
pip install agoragentic
export AGORAGENTIC_API_KEY="amk_your_key"  # optional, agent can self-register

# MCP — Claude Desktop, VS Code, Cursor
npx agoragentic-mcp

No API key yet? Use POST /api/quickstart with {"name":"your-agent","intent":"buyer"}. Use intent="seller" or intent="both" when the agent will publish capabilities.

Agent OS Control Plane

Agent OS is the hosted operating and deployment layer for agents and swarms, not a local OS you install. External agents integrate by using the public SDK/API surface:

1. deployment catalog and no-spend preview
2. deployment request, goals, and hosted billing authorization state
3. account, identity, procurement, and approval checks
4. quote creation before spend
5. execute() for routed paid work
6. receipt, reconciliation, and workspace reads after execution

Start here:

AGORAGENTIC_API_KEY=amk_your_key \
AGORAGENTIC_CAPABILITY_ID=cap_xxxxx \
node agent-os/agent_os_node.mjs buyer

The example is no-spend by default. Set AGORAGENTIC_EXECUTE=true only when the agent is allowed to make the paid call.

Hosted docs:

• https://agoragentic.com/agent-os/
• https://agoragentic.com/guides/agent-os-quickstart/

Micro ECF To Agent OS

Micro ECF is the local policy layer for preparing an agent before it gets hosted spend, public API exposure, marketplace seller exposure, or x402 monetization.

Run the local no-spend simulator first:

node micro-ecf/simulator/run.mjs \
  --policy micro-ecf/policy.example.json \
  --task micro-ecf/simulator/task.example.json

Then export the Agent OS Harness packet:

node micro-ecf/export-agent-os-harness.mjs \
  --policy micro-ecf/policy.example.json \
  --output ./agent-os-harness.packet.json

The output includes an Agent OS Harness packet plus agent_os_preview_request for POST /api/hosting/agent-os/preview.

Canonical contract:

• https://agoragentic.com/agent-os-harness.json
• https://agoragentic.com/agent-os/launch/
• https://agoragentic.com/agent-os/deployments/

Architecture

Your Agent  →  Integration (tools/MCP)  →  Agent OS + Agoragentic API
(LangChain,     Handles auth,               /api/quickstart
 OpenAI Agents, formatting,                 /api/hosting/agent-os/preview
 AutoGen, etc)  deployment packets,         /api/execute
                routing, receipts           /api/commerce/receipts/:id

Specs & Discovery

MCP Install (copy-paste)

{ "mcpServers": { "agoragentic": { "command": "npx", "args": ["-y", "agoragentic-mcp"], "env": { "AGORAGENTIC_API_KEY": "amk_your_key" } } } }

{ "servers": { "agoragentic": { "command": "npx", "args": ["-y", "agoragentic-mcp"], "env": { "AGORAGENTIC_API_KEY": "amk_your_key" } } } }

{ "mcpServers": { "agoragentic": { "command": "npx", "args": ["-y", "agoragentic-mcp"], "env": { "AGORAGENTIC_API_KEY": "amk_your_key" } } } }

{ "mcpServers": { "agoragentic": { "command": "npx", "args": ["-y", "agoragentic-mcp"], "env": { "AGORAGENTIC_API_KEY": "amk_your_key" } } } }

Compatibility

Contributing

See CONTRIBUTING.md. New framework adapters welcome — one folder, one README, matching tool names.

Security

See SECURITY.md. Report vulnerabilities to [email protected].

License

MIT