Git vs Opportunity MCP
A side-by-side look at the Git and Opportunity MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Git for version control work as a local process; choose Opportunity MCP for education as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Git when
- You need dedicated capabilities in the Version Control domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: No auth required.
- You want tools like
repo_path, context_lines, target.
Choose Opportunity MCP when
- You need dedicated capabilities in the Education domain.
- You prefer a local stdio subprocess transport.
- You want tools like
search_opportunities, get_opportunity, list_latest.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Version Control | Education |
| Quality signal | 81/100 · Excellent | 52/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | No auth required | Not declared |
| Pricing | Free | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Verified | Community listing |
| GitHub stars | 91,512 | 1 |
| Directory activity | 49 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 16 | 6 |
| Full listing | View Git | View Opportunity MCP |
Tools & capabilities
Git tools 16
repo_pathcontext_linestargetmessageMERGE_HEADHEADfilesmax_countstart_timestampend_timestampbranch_namebase_branch- +4 more on the listing page
Opportunity MCP tools 6
search_opportunitiesFull-text search across all indexed opportunities with optional filters.get_opportunityRetrieve full details for a single opportunity by its ID.list_latestNewest opportunities across all sources, sorted by post date.list_upcoming_deadlinesOpportunities closing within `N` days, sorted by deadline.list_sourcesList indexed sources, item counts, and last-refresh timestamps.refresh_indexRe-fetch sources on demand. Optional `source` argument limits the refresh to one site.
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
{
"mcpServers": {
"git": {
"command": "uvx",
"args": [
"installations"
]
}
}
}
Opportunity MCP
{
"mcpServers": {
"opportunity-mcp": {
"command": "uvx",
"args": [
"opportunity-mcp"
]
}
}
}
Frequently asked questions
Git is categorized under Version Control and uses a local stdio subprocess. Opportunity MCP belongs to Education and uses a local stdio subprocess. Pick Git for version control work and Opportunity MCP for education.
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 is listed as free. Auth: no auth required. Opportunity MCP 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 and opportunity-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Git has a quality signal of 81/100 (Excellent) with 49 views, 0 installs and 91,512 GitHub stars. Opportunity MCP has 52/100 (Good) with 2 views, 0 installs and 1 GitHub stars.