xerrameca
Xerrameca
独立的智能体间编排服务。
Xerrameca 协调自主智能体之间的结构化对话:轮次、租约、回合、延迟、完成共识、监督和被动监控。它通过公共 HTTP 适配器暴露 REST 和 MCP 接口,并与 Pluribus 集成以处理身份、权限以及可选的长期 Brain 摘要。
设计规则
Xerrameca 是一项独立服务。它不导入 Pluribus 内部实现、不打开 Pluribus SQLite 数据库,也不直接写入 Brain 数据表。
Agents / MCP / REST
|
v
+------------------------+
| Xerrameca |
| conversations / turns |
| leases / rounds |
| passive monitor |
| own SQLite database |
+-----------+------------+
|
ports / HTTP adapters
|
v
+------------------------+
| Pluribus |
| identity / permissions |
| optional Brain memory |
+------------------------+如果 Xerrameca 停止运行或发生故障,Pluribus 必须保持健康。
Related MCP server: MachineHearts
当前能力
独立的 SQLite 持久化
双智能体交替对话协议
claim/lease 保护与超时检查
回合与可配置延迟
完成提议 + 第二智能体确认
监督模式
发起人/管理员取消
REST command/inbox/claim/reply 接口
恰好七个独立的 MCP 工具
使用公共
/v1/identity/*API 的 Pluribus 身份适配器使用公共
/v1/memory/write的可选 Brain 摘要适配器可重试的摘要发件箱,无法回滚终态对话
仅限管理员的被动监控
非 root Docker 镜像与加固的 systemd 基线
真实的双智能体 X3 认证冒烟脚本
旧的 Pluribus webhook 推送 Runner 有意不包含在强制核心中。可选的推送投递单独跟踪,且必须使用未来的投递端口而非 Pluribus 内部实现。
本地运行
python3 -m venv .venv
. .venv/bin/activate
pip install -e '.[test]'
cp .env.example .env
uvicorn xerrameca.app:app --host 127.0.0.1 --port 8791然后:
GET http://127.0.0.1:8791/health
POST http://127.0.0.1:8791/mcp/对于由 Pluribus 支持的身份,请配置 XERRAMECA_IDENTITY_PROVIDER=pluribus 以及可访问的 PLURIBUS_BASE_URL。
智能体兼容性契约
REST:
POST /v1/xerrameca/commandGET /v1/xerrameca/inboxPOST /v1/xerrameca/turns/{turn_id}/claimPOST /v1/xerrameca/turns/{turn_id}/reply会话的 list/get/messages 端点
MCP:
xerrameca_commandxerrameca_inboxxerrameca_claimxerrameca_replyxerrameca_listxerrameca_getxerrameca_messages
面向智能体的调用使用 X-API-Key。X-Agent-ID 是可选的,不能覆盖凭据解析出的身份。
完整客户端契约请参见 docs/AGENT_INTEGRATION.md。
路线图
✅ X0 — 引导与提取契约
✅ X1 — 独立的拉取模式核心、REST/MCP 与被动监控
◐ X2 — Pluribus HTTP 适配器: 实现已合并;真实提供方认证待完成
◐ X3 — 独立部署: 打包/runbook 已合并;真实部署/E2E 认证待完成
⏳ X4 — Pluribus 清理: 仅在 X3 认证之后
可选的推送/webhook 投递单独跟踪,不会阻塞拉取模式的独立服务。
文档
docs/ARCHITECTURE.mddocs/PLURIBUS_INTEGRATION.mddocs/AGENT_INTEGRATION.mddocs/DEPLOYMENT.md
许可证
Apache-2.0.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- FlicenseAqualityDmaintenanceAn MCP server that enables LLMs to interact with Agent-to-Agent (A2A) protocol compatible agents, allowing for sending messages, tracking tasks, and receiving streaming responses.528
- Alicense-qualityDmaintenanceMCP server that gives AI agents the ability to discover, match with, and build relationships with other autonomous agents. Supports agent registration, matchmaking, messaging, shared goals, relationship lifecycle management, and real-time event subscriptions.51MIT

Agorus MCP Serverofficial
Alicense-qualityDmaintenanceMCP server for the Agorus AI agent marketplace, exposing API operations as tools for LLMs to discover, contract, and interact with agents and services.15MIT- AlicenseAqualityCmaintenanceMCP server for multi-agent AI systems providing mailbox messaging, A2A task delegation, resource coordination, and a web dashboard.2116MIT
Related MCP Connectors
Hosted AgentLux MCP server for marketplace, identity, creator, services, and social flows.
MCP server for AI agents to plan, verify, and deploy Cloudflare-native apps.
Agent Orchestrator MCP Server by MEOK AI Labs
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/spicouc/xerrameca'
If you have feedback or need assistance with the MCP directory API, please join our Discord server