Concord MCP vs Dispatch
A side-by-side look at the Concord MCP and Dispatch MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Concord MCP for coding agents work over a hosted endpoint; choose Dispatch for coding agents. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Concord MCP when
- You need dedicated capabilities in the Coding Agents domain.
- You prefer a remote HTTP/SSE transport.
- You have the keys it needs:
CONCORD_REPO_ROOT.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Coding Agents | Coding Agents |
| Quality signal | 45/100 · Fair | 31/100 · Emerging |
| Install command | Confirmed | Not confirmed yet |
| Transport | Remote HTTP/SSE | — |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | CONCORD_REPO_ROOT | None listed |
| Verified owner |
Tools & capabilities
Concord MCP tools
No tool names declared yet. Check the project README from the listing page.
Dispatch 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.
Concord MCP
{
"mcpServers": {
"concord-mcp": {
"url": "https://api.star-history.com/chart?repos=Get-Concord-AI/concord-mcp&type=date&theme=dark&legend=top-left&sealed_token=PLqZk9LDZSite53TJb5bwyYask4-B5wAFxLcp3Ki_mJ3KlMtSpH09lN3ohwJuoQNs5Kwg_0zPG2DEwcRzJZvCIP1Md6vMdHjNwF_WkjuX6gd44wkwWFzqrAWgXGx2bPFEuJFRhmuWUlbRLnPOw6uW7cVJzrlcxprXCDU3_hHmUlHaFjVjQulH7EkfyuA"
}
}
}
Dispatch
No confirmed install command for Dispatch yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
Concord MCP is categorized under Coding Agents and uses a remote HTTP/SSE transport. Dispatch belongs to Coding Agents and uses an install path we have not confirmed yet. Pick Concord MCP for coding agents work and Dispatch 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. Dispatch has no confirmed install command yet — follow its own setup instructions.
Concord MCP has no declared pricing — check the project's own site. Dispatch 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 concord-mcp and dispatch as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Concord MCP has a quality signal of 45/100 (Fair) with 2 views, 0 installs and 453 GitHub stars. Dispatch has 31/100 (Emerging) with 0 views, 0 installs and 2 GitHub stars.