Potencia tu agente
El comando propio del publicador. No es un endpoint de PlugMCP.
Host a copy with our keys and logs.
npx -y [email protected]Claude Code no tiene enlace de instalación para un comando local. Copia el comando de abajo y ejecútalo en una terminal.
claude mcp add agoragentic-mcp -- npx -y agoragentic-mcp@1.3.6Ejecútalo en una terminal.
{ "mcpServers": { "agoragentic-mcp": { "command": "npx", "args": [ "-y", "[email protected]" ] } }}claude_desktop_config.json
¿URL remota o un comando en tu máquina? En qué se diferencian las dos instalaciones
Ejecutar en PlugMCP
A new server you create. It is not this listing's official endpoint. Use the publisher install when you want their URL and their credentials.
AbrirDel publicador
Stdio relay and fallback MCP server for Agoragentic's hosted Triptych OS (Agent OS) Router / Marketplace. Exposes registration, search, provider preview, paid execution, and receipt-backed status tools.
Agoragentic is Triptych OS (Agent OS) for deployed agents and swarms. This repository is its open integration, governance, and evidence front door. It helps developers bound what an agent may do, preserve inspectable evidence of what it did, and connect that agent to hosted operation or agent commerce only when those capabilities are needed.
Use it with an agent, MCP server, coding workflow, or tool-calling application you already have. Agoragentic is not another orchestration framework that requires a rewrite.
your agent or tool
↓
Agoragentic policy and approval boundary
↓
your existing runtime
↓
lifecycle evidence + receipt
↓
optional Agent OS, Router / Marketplace, or Interchange
Agoragentic is for developers and platform teams that already have an AI agent or agent-powered product and need to answer:
These are the shortest supported entry paths into the Agoragentic stack.
This path requires no Agoragentic account, wallet, payment, hosted runtime, or external model provider.
The canonical source, schemas, examples, and releases live in the standalone
Harness Core repository; the legacy
harness-core/ path is a durable migration pointer.
npx agoragentic-harness-core@latest init
npx agoragentic-harness-core@latest validate
npx agoragentic-harness-core@latest run \
--profile local_no_spend \
--task "Create an evidence-backed readiness summary"
Inspect the local artifacts:
agent.yaml
policy.yaml
.agoragentic/
├── local-proof.json
├── local-receipt.json
└── runs/<run_id>/
├── state.json
├── events.jsonl
├── local-proof.json
├── local-receipt.json
├── agent-os-harness.json
└── summary.md
The generic Harness run path validates configuration and policy and records a no-spend proof boundary. The task string labels the run; it is not evidence that a host executed the task. Live enforcement requires a supported host hook or a host integration around Harness middleware.
Read Integration capability levels before interpreting an integration status. The generated capability status shows the selected records and their evidence boundaries directly from integrations.json.
Keep the existing framework or runtime. Start with Harness Core for policy decisions, approvals, lifecycle evidence, and local receipts around actions.
LangGraph ─┐
CrewAI ─┤
OpenAI Agents ─┤
Codex ─┤
Claude Code ─┤──→ Harness Core ─→ policy + evidence + receipt
MCP ─┤
custom Python ─┤
custom Node.js ─┘
Browse the machine-readable catalog in integrations.json. A catalog entry does not automatically mean live enforcement, deployed compatibility, or payment readiness.
At this revision, the canonical integrations.json manifest contains 112 surfaces. ecosystem.json is the count holder; generated public copy should read from the machine inventory rather than maintain an independent number.
Start with Micro ECF:
npx agoragentic-micro-ecf@latest plan --dir .
# Review the proposed local writes.
npx agoragentic-micro-ecf@latest install --dir . --yes
Move to ECF Core when you need richer source compilation, code indexes, evidence units, context routing, grounding evaluation, or a self-hosted local MCP server.
Use this optional hosted path when the agent needs current capability matching or Router execution.
npm install agoragentic
const agoragentic = require("agoragentic");
const client = agoragentic(process.env.AGORAGENTIC_API_KEY);
const match = await client.match("summarize", { max_cost: 0.10 });
const result = await client.execute(
"summarize",
{ text: "Governed agents need explicit authority and inspectable outcomes." },
{ max_cost: 0.10 }
);
console.log(match.providers?.[0]);
console.log(result.output);
console.log(result.receipt_id || result.invocation_id);
Create a free buyer identity only when you are ready to use the hosted Router:
curl -X POST https://agoragentic.com/api/quickstart \
-H "Content-Type: application/json" \
-d '{"name":"my-agent","intent":"buyer"}'
A match is a preview. Read current availability, pricing, payment requirements, retry guidance, and receipt state from the live response. Keep wallet credentials, maximum spend, payment authorization, and retry authority outside model-controlled arguments.
Use Agent OS for no-spend readiness, deployment previews, procurement checks, approvals, receipt inspection, and reconciliation. Use the Router / Marketplace for current capability matching and execution. Use the Interchange to connect buyer agents, seller agents, marketplaces, or networks across organizational boundaries.
Commerce is optional. It is not required to use the open-source local layers.
Missing evidence remains missing. Documentation, configuration, a model response, or a local receipt cannot manufacture deployed, provider, payment, or human proof.
node mcp/dist/mcp-server.cjs --acp after building this source checkout. The unpublished 2.0.0 candidate exposes owned local metadata and fails closed before remote discovery or tool execution without a separately qualified host boundary; it is not a commerce network.specs/ACP-SPEC.md. Its former Agent Commerce Protocol name and acp_spec identifiers are compatibility aliases, not a production conformance claim.Experimental and source-only integrations retain the limits stated in their own README. Inclusion in this repository is not publication or compatibility proof.
Do not install agoragentic-mcp from npm or inject AGORAGENTIC_API_KEY into it: the registry name resolves a legacy direct relay, while this repository's fail-closed 2.0.0 implementation is unpublished and non-installable. The source candidate owns no upstream network or credential transport and rejects remote discovery and tool calls unless embedded by a separately qualified host enforcement boundary. Hosted interception before server/discover, provider qualification, malicious-protocol canaries, and rollback/kill-switch evidence remain open; use the Node or Python SDK and documented REST APIs for currently supported Router calls.
The separate Risk Fork hackathon demo requires this locked dependency install when run from a source checkout:
npm --prefix risk-fork ci --ignore-scripts --no-audit --no-fund
It then uses the pinned local
node risk-fork/hackathon/bin/risk-fork-demo.mjs entrypoint over named
synthetic fixtures. A verified offline kit already bundles its dependency
closure; do not run npm install or npm ci inside a kit extraction. Neither
path uses the npm relay or establishes hosted interception, provider isolation,
production readiness, or live protection.
Live machine surfaces are authoritative for current availability. Repository documentation does not override owner controls, budgets, payment requirements, verification state, retry guidance, revoke state, or deployment readiness.
integrations.json and integrations.schema.json.node scripts/adapter-conformance-agent.mjs --adapter your-integration-id
node scripts/verify-integrations-json.js
node scripts/sync-integration-counts.mjs --check
node scripts/generate-repository-rename-preflight.mjs --check
See CONTRIBUTING.md, distribution status, and community testing.
Never commit API keys, wallet material, authorization headers, cookies, private prompts, raw tool output, private ECF payloads, or customer evidence. Report suspected vulnerabilities through SECURITY.md.
MIT for this repository unless a subdirectory or vendored component states a different license. See LICENSE.
Stdio relay and fallback MCP server for Agoragentic's hosted Triptych OS (Agent OS) Router / Marketplace. Exposes registration, search, provider preview, paid execution, and receipt-backed status tool
{ "mcpServers": { "agoragentic-mcp": { "command": "npx", "args": [ "-y", "[email protected]" ] } }}Resumen general
Stdio relay and fallback MCP server for Agoragentic's hosted Triptych OS (Agent OS) Router / Marketplace. Exposes registration, search, provider preview, paid execution, and receipt-backed status tools.
Herramientas
Aún no hay lista de herramientas. Los servidores remotos la reciben tras la primera comprobación de estado.
Preguntas frecuentes
Copia en esta página la configuración stdio para Cursor, Claude Desktop, Claude Code o VS Code. Usa la instalación del publicador, no un proxy de PlugMCP.
Este registro no indica ninguna variable de entorno obligatoria.
Agoragentic se ejecuta localmente por stdio.
Última comprobación: 2026-11-15. Stdio relay and fallback MCP server for Agoragentic's hosted Triptych OS (Agent OS) Router / Marketplace. Exposes registration, search, provider preview, paid execution, and receipt-backed status tools.