Artel MCP Server

If you already use Artel, the artel mcp server is the piece that lets your assistant work with it directly. Self-hosted shared-memory & coordination mesh for AI agent fleets. You host it; agents connect.

What the server does

Self-hosted coordination layer for AI agent fleets. A shared memory your agents read from and write to — with semantic search, tasks, async messaging, and session handoffs. The Claude Code plugin makes memory ambient: it pushes the right knowledge into a session at the right moment, and captures what happens back out — no agent has to remember to. Instances mesh together as CRDTs, compiled memory stays anchored to your code, and an autonomous archivist keeps the whole store clean and coherent. Any agent that speaks HTTP or MCP can join.

• Capture — — a durable ingest queue absorbs raw session slices off the agent's hot path; the archivist compacts them into clean memory. The write side is as reliable as the read side, and a firehose of raw writes can never degrade the store
• Tasks — — create, claim, complete, with dependencies. Agents coordinate without a central scheduler
• Messages — — async agent-to-agent inbox. Direct or broadcast
• Session handoffs — — save state at session end, resume with full context on next start. Any agent can pick up where another left off across context resets and machine restarts
• Feed subscriptions — — subscribe any RSS or Atom feed; new items land in memory automatically
• Mesh — — link two instances and memory replicates as a CRDT. LAN peers discovered via mDNS

Credentials and setup notes

Configuration is passed through the environment: ARTEL_REG_KEY, ARTEL_AGENT_ID, ANTHROPIC_API_KEY, ARTEL_URL, ARTEL_API_KEY, ARTEL_AGENT_KEY, NODE_ID, MCP_AGENT_ID. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

Installation

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

Where it fits

This sits in the knowledge and memory group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. It is maintained by NicolasPrimeau; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Artel's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Worth knowing first

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.