Concord MCP vs Grok Build
A side-by-side look at the Concord MCP and Grok Build 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 Grok Build 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 Concord MCP when
- You need dedicated capabilities in the Coding Agents domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: No auth required.
Choose Grok Build when
- You need dedicated capabilities in the Coding Agents domain.
- You prefer a local stdio subprocess transport.
- You want tools like
grok, review, websearch.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Coding Agents | Coding Agents |
| Quality signal | 66/100 · Great | 53/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 664 | 0 |
| Directory activity | 4 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | 8 |
| Full listing | View Concord MCP | View Grok Build |
Tools & capabilities
Concord MCP tools
No tool names declared yet. Check the project README from the listing page.
Grok Build tools 8
grokRun a headless Grok agent. Prompt, session resume/continue/fork, model, effort, tool allow/denyreviewReview a git diff: working tree, a merge-base diff against a ref, or a single commitwebsearchResearch a question on the web, and report which searches and sources it actually usedstatusPoll a background run, or list recent onesstopTerminate a background run's process treesessionsList, search, and look up the Grok sessions on this machinecheckServer version, resolved binary, `grok version`, auth, permission ceiling, run defaultshelpgrok --help` passthrough
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"
}
}
}
Grok Build
{
"mcpServers": {
"grok-build": {
"command": "npx",
"args": [
"-y",
"grok-build-mcp-server"
]
}
}
}
Frequently asked questions
Concord MCP is categorized under Coding Agents and uses a remote HTTP/SSE transport. Grok Build belongs to Coding Agents and uses a local stdio subprocess. Pick Concord MCP for coding agents work and Grok Build 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.
Concord MCP is listed as free. Auth: no auth required. Grok Build 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 grok-build 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 66/100 (Great) with 4 views, 0 installs and 664 GitHub stars. Grok Build has 53/100 (Good) with 0 views, 0 installs and 0 GitHub stars.