Apra MCP Server

Apra MCP server is a hosted integration for AI assistants that speak the Model Context Protocol. MCP server for orchestrating multiple agentic AI instances (Claude, Gemini, Codex, Copilot, AGY) across machines via SSH.

What you get

• Which machine runs which agent? — Real devices, not throwaway sandboxes:
• Which model does which job? — Claude for review, a cheap tier for
• Who watches the agents? — Durable workflows with supervisors, watchdogs,
• Who holds the keys? — Secrets entered out-of-band, never visible to any

What the assistant can call

Once Apra is connected, these are the calls the assistant has available:

• Multi — cycle sprints running for hours, unattended
• Members — real machines running provider CLIs. The server composes
• Supervisor — the always-on layer -- launch and stop sprints over HTTP,
• Releases — GitHub Releases
• Issues — GitHub Issues
• Pillar — Concretely
• Package — What it is
• apra-fleet — The fleet platform: server, CLI, member management, credentials, workflows runtime
• Topic — Link
• FAQ — docs/FAQ.md
• Troubleshooting — docs/troubleshooting.md
• Architecture — docs/architecture.md

Setting it up

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

Choosing this one

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. Apra's toolset — Multi, Members, Supervisor and 9 more — is a fair guide to whether it matches your workflow. It is maintained by kumaakh; worth a glance at recent repository activity before you build anything load-bearing on it.

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

Before you rely on it

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• With 12 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Apra.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the apra mcp server does with a few real requests.