Opportunity MCP vs Git
A side-by-side look at the Opportunity MCP and Git MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Opportunity MCP for education work as a local process; choose Git 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 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.
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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Education | Version Control |
| Quality signal | 52/100 · Good | 81/100 · Excellent |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Verified |
| GitHub stars | 1 | 91,512 |
| Directory activity | 2 views 0 installs 0 upvotes | 49 views 0 installs 0 upvotes |
| Tools | 6 | 16 |
| Full listing | View Opportunity MCP | View Git |
Tools & capabilities
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.
Git tools 16
repo_pathcontext_linestargetmessageMERGE_HEADHEADfilesmax_countstart_timestampend_timestampbranch_namebase_branch- +4 more on 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.
Opportunity MCP
{
"mcpServers": {
"opportunity-mcp": {
"command": "uvx",
"args": [
"opportunity-mcp"
]
}
}
}
Git
{
"mcpServers": {
"git": {
"command": "uvx",
"args": [
"installations"
]
}
}
}
Frequently asked questions
Opportunity MCP is categorized under Education and uses a local stdio subprocess. Git belongs to Version Control and uses a local stdio subprocess. Pick Opportunity MCP for education work and Git 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.
Opportunity MCP has no declared pricing — check the project's own site. Git is listed as free. Auth: no auth required. 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 opportunity-mcp and git as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Opportunity MCP has a quality signal of 52/100 (Good) with 2 views, 0 installs and 1 GitHub stars. Git has 81/100 (Excellent) with 49 views, 0 installs and 91,512 GitHub stars.