GitHub Issue MCP vs Taken
A side-by-side look at the GitHub Issue MCP and Taken MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose GitHub Issue MCP for version control work as a local process; choose Taken 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 GitHub Issue MCP when
- You need dedicated capabilities in the Version Control domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
GITHUB_TOKEN, GITHUB_OWNER, GITHUB_REPO, GEMINI_API_KEY, GEMINI_MODEL, GEMINI_MAX_RETRIES, GEMINI_RETRY_BASE_DELAY, DEBUG.
Choose Taken 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 | 41/100 · Fair | 40/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 | GITHUB_TOKENGITHUB_OWNERGITHUB_REPOGEMINI_API_KEYGEMINI_MODELGEMINI_MAX_RETRIESGEMINI_RETRY_BASE_DELAYDEBUG | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 2 |
| Directory activity | 1 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View GitHub Issue MCP | View Taken |
Tools & capabilities
GitHub Issue MCP tools
No tool names declared yet. Check the project README from the listing page.
Taken 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.
GitHub Issue MCP
{
"mcpServers": {
"github-issue-mcp": {
"command": "npx",
"args": [
"-y",
"github-issue-mcp"
],
"env": {
"GITHUB_TOKEN": "YOUR_GITHUB_TOKEN_HERE",
"GITHUB_OWNER": "YOUR_GITHUB_OWNER_HERE",
"GITHUB_REPO": "YOUR_GITHUB_REPO_HERE",
"GEMINI_API_KEY": "YOUR_GEMINI_API_KEY_HERE",
"GEMINI_MODEL": "YOUR_GEMINI_MODEL_HERE",
"GEMINI_MAX_RETRIES": "YOUR_GEMINI_MAX_RETRIES_HERE",
"GEMINI_RETRY_BASE_DELAY": "YOUR_GEMINI_RETRY_BASE_DELAY_HERE",
"DEBUG": "YOUR_DEBUG_HERE"
}
}
}
}
Taken
{
"mcpServers": {
"taken": {
"command": "uvx",
"args": [
"--from",
"taken-gh",
"taken-mcp"
]
}
}
}
Frequently asked questions
GitHub Issue MCP is categorized under Version Control and uses a local stdio subprocess. Taken belongs to Version Control and uses a local stdio subprocess. Pick GitHub Issue MCP for version control work and Taken 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.
GitHub Issue MCP has no declared pricing — check the project's own site. Taken 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 github-issue-mcp and taken as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, GitHub Issue MCP has a quality signal of 41/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. Taken has 40/100 (Fair) with 0 views, 0 installs and 2 GitHub stars.