Artel
Coordinate multiple AI agents with self-hosted shared memory and a coordination mesh instead of ad-hoc chat logs.
Overview
Artel is an MCP server for the Build phase that provides a self-hosted shared-memory and coordination mesh for multi-agent fleets.
What is this MCP server?
- Self-hosted shared-memory and coordination mesh for AI agent fleets (you host; agents connect)
- Remote MCP over streamable HTTP at https://{artel_host}/mcp
- Auth headers: X-Agent-Id and secret X-Api-Key per agent on your instance
- artel_host variable defaults to public demo artel.run; production use expects your own host
- Open-source repo on GitHub; server schema version 0.17.1
- Remote transport: streamable-http
- Default demo host variable: artel.run
Community signal: 3 GitHub stars.
What problem does it solve?
Multi-agent side projects fall apart when each agent keeps private context and nothing reliable synchronizes decisions across the fleet.
Who is it for?
Solo builders running several specialized agents against one product who can self-host a coordination endpoint.
Skip if: Single-agent coding sessions or teams unwilling to run and secure their own Artel host.
What do I get? / Deliverables
After you deploy Artel and register the remote MCP URL, agents share coordinated memory on your instance so parallel agent work stays aligned.
- Remote MCP endpoint on your artel_host for agent connections
- Shared coordination and memory layer across registered agents
- Documented agent credentials mapped to fleet roles
Recommended MCP Servers
Journey fit
Artel belongs in Build when you are assembling multi-agent workflows and need durable shared state while features are still taking shape. Agent-tooling captures a fleet coordination MCP endpoint; self-hosting the mesh is infrastructure, but the catalog shelf is enabling agent systems.
How it compares
Fleet coordination MCP mesh, not a single-repo code-graph tool or generic task queue skill.
Common Questions / FAQ
Who is Artel for?
Developers building multi-agent systems who want self-hosted shared memory exposed over MCP HTTP.
When should I use Artel?
Use it during Build when two or more agents must share state, handoffs, or coordination beyond one chat thread.
How do I add Artel to my agent?
Point your agent’s remote MCP config to https://your-artel-host/mcp with streamable HTTP and set X-Agent-Id plus X-Api-Key for each agent.