Mcacp vs Timps Swarm
A side-by-side look at the Mcacp and Timps Swarm MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Mcacp for coding agents work as a local process; choose Timps Swarm for coding agents as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Mcacp when
- You need dedicated capabilities in the Coding Agents domain.
- You prefer a local stdio subprocess transport.
- You want tools like
list_installed_agents, registry_search, agent_install.
Choose Timps Swarm when
- You need dedicated capabilities in the Coding Agents domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Coding Agents | Coding Agents |
| Quality signal | 52/100 · Good | 40/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 11 | 1 |
| Directory activity | 0 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 23 | Not listed |
| Full listing | View Mcacp | View Timps Swarm |
Tools & capabilities
Mcacp tools 23
list_installed_agentsList locally installed agentsregistry_searchSearch the ACP agent registryagent_installInstall an agent from the registryagent_uninstallRemove an installed agentagent_check_upgradesCheck for available upgradesdiscover_agentsScan editor configs (Zed, JetBrains) for agentsreload_configReload `mcacp.json` from diskinitializeSpawn an agent process and perform the ACP handshakeshutdownGracefully shut down an agentnew_sessionCreate a session with working directory and permission policyload_sessionResume a persisted sessionlist_sessionsList stored sessions for an agent- +11 more on the listing page
Timps Swarm tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Mcacp
{
"mcpServers": {
"mcacp": {
"command": "npx",
"args": [
"-y",
"mcacp"
]
}
}
}
Timps Swarm
{
"mcpServers": {
"timps-swarm": {
"command": "npx",
"args": [
"-y",
"timps-swarm"
]
}
}
}
Frequently asked questions
Mcacp is categorized under Coding Agents and uses a local stdio subprocess. Timps Swarm belongs to Coding Agents and uses a local stdio subprocess. Pick Mcacp for coding agents work and Timps Swarm for coding agents.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Mcacp has no declared pricing — check the project's own site. Timps Swarm has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add mcacp and timps-swarm as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Mcacp has a quality signal of 52/100 (Good) with 0 views, 0 installs and 11 GitHub stars. Timps Swarm has 40/100 (Fair) with 0 views, 0 installs and 1 GitHub stars.