Git History vs Solumbe
A side-by-side look at the Git History and Solumbe MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Git History for version control work as a local process; choose Solumbe 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 Git History when
- You need dedicated capabilities in the Version Control domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
GIT_REPO_PATH. - You want tools like
search_commits, get_recent_commits, get_commit_diff.
Choose Solumbe 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 | ||
|---|---|---|
| Category | Version Control | Version Control |
| Quality signal | 61/100 · Good | 45/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 | GIT_REPO_PATH | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 2 |
| Directory activity | 3 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 7 | Not listed |
| Full listing | View Git History | View Solumbe |
Tools & capabilities
Git History tools 7
search_commitsEtsii Git-commiteja joiden commit-viesti sisältää annetun hakusanan (esim. bugin numero tai avainsana). Käytä tätä kun haluat selvittää MIKSI jokin muutos tehtiin.get_recent_commitsHakee repositorion uusimmat commitit uusimmasta vanhimpaan. Käytä kun haluat yleiskuvan siitä, mitä projektissa on viime aikoina tehty.get_commit_diffHakee tietyn commitin koko diffin (kaikki tiedostomuutokset). Käytä kun haluat nähdä TARKALLEEN mitä muuttui.get_file_historyHakee tiedoston muutoshistorian: milloin sitä on muokattu, kuka muokkasi ja mihin commit-viestiin muutos liittyi. Käytä kun haluat selvittää MILLOIN ja KUKA muokkasi tiettyä tiedostoa viimeksi.blame_fileHakee tiedoston rivikohtaisen 'git blame' -tiedon: kuka ja missä commitissa kunkin rivin viimeksi kirjoitti. Käytä kun haluat selvittää KUKA kirjoitti tietyn rivin ja MISSÄ commitissa se tuli mukaan.get_contributorsHakee yhteenvedon repositorion committaajista ja heidän commit-määristään (kuten 'git shortlog -sn'). Käytä kun haluat yleiskuvan siitä, KEITÄ projektissa on ollut mukana ja kuinka aktiivisia he ovat olleet.get_diff_between_refsHakee diffin kahden commitin, branchin tai tagin välillä, valinnaisesti rajattuna yhteen tiedostoon. Käytä kun haluat verrata kahta pistettä historiassa (esim. kahta branchia tai releasea), et vain yhtä commitia.
Solumbe 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.
Git History
{
"mcpServers": {
"git-history": {
"command": "npx",
"args": [
"-y",
"mcp-server-git-history"
],
"env": {
"GIT_REPO_PATH": "YOUR_GIT_REPO_PATH_HERE"
}
}
}
}
Solumbe
{
"mcpServers": {
"solumbe": {
"command": "npx",
"args": [
"-y",
"@bashbop/solumbe"
]
}
}
}
Frequently asked questions
Git History is categorized under Version Control and uses a local stdio subprocess. Solumbe belongs to Version Control and uses a local stdio subprocess. Pick Git History for version control work and Solumbe for version control.
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.
Git History has no declared pricing — check the project's own site. Solumbe 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 git-history and solumbe as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Git History has a quality signal of 61/100 (Good) with 3 views, 0 installs and 0 GitHub stars. Solumbe has 45/100 (Fair) with 0 views, 0 installs and 2 GitHub stars.