Categories › AI & Agents › Multi-agent, orchestration & workflows
Deliberation primitive for multi-agent coordination: cruxes, vote clustering, consensus.
Remote server: your requests and data go to gemot.dev. Claude Code: claude mcp add --transport http gemot-deliberation-server https://gemot.dev/mcp · Claude app: Settings → Connectors → Add custom connector.
The tools this server listed when we connected to it, in its own words.
account — Fund your gemot credit balance. Actions: - buy_credits: Top up THIS API key's balance over the ATXP/x402 rail (optional: pack, atxp_account_admin — Admin and audit tools. Actions: - report_abuse: Report abusive content (deliberation_id, reason) - get_audit_log: Get audit trail incl. tampanalyze — Analyze disagreements and find common ground. Actions: - run: Trigger analysis — extracts cruxes, clusters, consensus (deliberation_id; opticoordinate — Multi-agent coordination. Actions: - delegate: Delegate your vote to another agent (deliberation_id, from_agent, to_agent; optional: scope) decide — Commitments and reputation tracking. Actions: - commit: Commit to a deliberation outcome (deliberation_id, agent_id, statement; optional: codeliberation — Manage deliberations. Actions: - create: Create a new deliberation (topic, description, template, group_id, deadline_minutes, rules, visibilparticipate — Participate in a deliberation. Actions: - submit_position: Submit your position (deliberation_id, agent_id, content; optional: model_family,Not tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.