Bourdon vs Stateark
A side-by-side look at the Bourdon and Stateark MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Bourdon for version control work; choose Stateark for version control as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Stateark when
- You need dedicated capabilities in the Version Control domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | B Bourdon | |
|---|---|---|
| Category | Version Control | Version Control |
| Quality signal | 37/100 · Fair | 43/100 · Fair |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | 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 | — | 2 |
| Directory activity | 0 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View Bourdon | View Stateark |
Tools & capabilities
Bourdon tools
No tool names declared yet. Check the project README from the listing page.
Stateark 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.
Bourdon
No confirmed install command for Bourdon yet — follow the setup steps linked from its listing page rather than a guessed package name.
Stateark
{
"mcpServers": {
"stateark": {
"command": "npx",
"args": [
"-y",
"stateark"
]
}
}
}