orgopolis-cli

Validate A2A v1.0 Agent Cards and import them into Orgopolis.

npm install -g orgopolis-cli
orgo validate https://agents.example.com/.well-known/agent-card.json --auth-bearer sk_agent_...
orgo config set-key org_live_...
orgo push https://agents.example.com/.well-known/agent-card.json --auth-bearer sk_agent_...
orgo agents set-credentials billing-agent --auth-api-key agent_key_...

orgo uses https://mcp.orgopolis.com/ by default.

Dashboard sign-in is passwordless. Orgopolis dashboard users sign in with a one-time magic link emailed from [email protected]. Sessions last 60 days. The orgo CLI does not use magic links — CLI clients and dashboard users have separate credentials (API keys vs. email).

Live Progress + Steering

The Orgopolis MCP server streams progress for every running goal run over Server-Sent Events and supports live steering.

Before an MCP chat assistant calls goal, it should clarify ambiguous user requests, confirm the final goal with the user, and include the desired outcome, scope, constraints, and success criteria in the submitted goal text.

# Watch a goal run as it executes (no auth required, runId is a 122-bit UUID)
curl -N https://mcp.orgopolis.com/runs/<runId>/events

# Or use the structured MCP tool surface
# 1. Start a task and get a runId back
# tools/call { name: "goal", arguments: { goal: "Confirmed with the user: ..." } }
# 2. Poll structured progress
# tools/call { name: "goal_status", arguments: { runId: "..." } }
# 3. Inject a follow-up note that the orchestrator picks up on its next LLM call
# tools/call { name: "goal_steer", arguments: { runId: "...", note: "Try the briefing agent instead." } }

See https://app.orgopolis.com/docs#mcp-tools for the full MCP tool reference.