Gitscrum Core MCP vs MCP Linear
A side-by-side look at the Gitscrum Core MCP and MCP Linear MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Gitscrum Core MCP for product management work as a local process; choose MCP Linear for product management as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Gitscrum Core MCP when
- You need dedicated capabilities in the Product Management domain.
- You prefer a local stdio subprocess transport.
- You want tools like
task, sprint, workspace.
Choose MCP Linear when
- You need dedicated capabilities in the Product Management domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
LINEAR_API_TOKEN, LINEAR_OAUTH_ACCESS_TOKEN.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Product Management | Product Management |
| Quality signal | 57/100 · Good | 51/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | Free |
| Required env vars | None listed | LINEAR_API_TOKENLINEAR_OAUTH_ACCESS_TOKEN |
| Verified owner | Community listing | Community listing |
| GitHub stars | 5 | 147 |
| Directory activity | 0 views 0 installs 0 upvotes | 3 views 0 installs 0 upvotes |
| Tools | 29 | Not listed |
| Full listing | View Gitscrum Core MCP | View MCP Linear |
Tools & capabilities
Gitscrum Core MCP tools 29
task[tasks](docs/tools/tasks.md)sprint[sprints](docs/tools/sprints.md)workspace[projects](docs/tools/projects.md)project[projects](docs/tools/projects.md)time[time-tracking](docs/tools/time-tracking.md)user_story[user-stories](docs/tools/user-stories.md)epic[epics](docs/tools/epics.md)label[labels](docs/tools/labels.md)task_type[task-types](docs/tools/task-types.md)workflow[workflows](docs/tools/workflows.md)discussion[discussions](docs/tools/discussions.md)comment[comments](docs/tools/comments.md)- +17 more on the listing page
MCP Linear 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.
Gitscrum Core MCP
{
"mcpServers": {
"mcp-93": {
"command": "npx",
"args": [
"-y",
"@gitscrum-studio/mcp-server"
]
}
}
}
MCP Linear
{
"mcpServers": {
"tacticlaunch-mcp-linear": {
"command": "npx",
"args": [
"-y",
"@tacticlaunch/mcp-linear"
],
"env": {
"LINEAR_API_TOKEN": "YOUR_LINEAR_API_TOKEN_HERE",
"LINEAR_OAUTH_ACCESS_TOKEN": "YOUR_LINEAR_OAUTH_ACCESS_TOKEN_HERE"
}
}
}
}
Frequently asked questions
Gitscrum Core MCP is categorized under Product Management and uses a local stdio subprocess. MCP Linear belongs to Product Management and uses a local stdio subprocess. Pick Gitscrum Core MCP for product management work and MCP Linear for product management.
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.
Gitscrum Core MCP has no declared pricing — check the project's own site. MCP Linear is listed as free. Auth: api key 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 mcp-93 and tacticlaunch-mcp-linear as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Gitscrum Core MCP has a quality signal of 57/100 (Good) with 0 views, 0 installs and 5 GitHub stars. MCP Linear has 51/100 (Good) with 3 views, 0 installs and 147 GitHub stars.