GitHub
GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.
Description from the maker (original English)
Safety-aware MCP server for Linear issues, projects, cycles, and dependencies.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
LINEAR_API_KEYValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"abscissa": {
"command": "uvx",
"args": [
"abscissa"
],
"env": {
"LINEAR_API_KEY": "your-value"
}
}
}
}Run this in your terminal
claude mcp add abscissa --env LINEAR_API_KEY=your-value -- uvx abscissaFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"abscissa": {
"command": "uvx",
"args": [
"abscissa"
],
"env": {
"LINEAR_API_KEY": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"abscissa": {
"type": "stdio",
"command": "uvx",
"args": [
"abscissa"
],
"env": {
"LINEAR_API_KEY": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account KazKozDev, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: LINEAR_API_KEY
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.1.3) reached the registry 4 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.
In the same category: GitHub, Desktop Commander, Cloudflare MCP
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.
MCP server for terminal commands, file operations, and process management
Cloudflare MCP servers
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Abscissa is a Python stdio MCP server for Linear. It turns Linear's GraphQL API into 42 tools for an MCP client: issues, projects, cycles, dependencies, comments, labels, workflow states, teams, and users.
The design priority is deliberate control over project data. Read operations return cursor-paginated results; get_user_issues() resolves the authenticated Linear user; archive and delete tools require an explicit confirm=true before they make a destructive API call. The server stores no credentials and reads LINEAR_API_KEY from its process environment.
Abscissa uses the stdio transport from the Model Context Protocol. Any client that supports stdio MCP can launch it as a local tool process.
You need Python 3.10+ and a Linear personal API key.
git clone https://github.com/KazKozDev/abscissa.git
cd abscissa python3 -m venv .venv .venv/bin/pip install -e '.[dev]' export LINEAR_API_KEY='lin_api_…' .venv/bin/abscissa
You can also install Abscissa directly from PyPI:
pip install abscissa
The final command starts the MCP server on standard input and output. Register .venv/bin/abscissa as a stdio command in your MCP client, and pass LINEAR_API_KEY through that client's environment or secret manager.
The key remains outside the repository. The .gitignore excludes common local environment files, including .env and .venv.
Once Abscissa is registered in your MCP client, try prompts like:
Show my open Linear issues grouped by project.
Create an issue in ENG for fixing onboarding copy. List issues blocked by GEN-32.
| Area | Tools |
|---|---|
| Identity | get_current_user |
| Issues | create_issue, update_issue, search_issues, get_user_issues, get_issue, assign_issue, add_comment, set_issue_estimate |
| Issue lifecycle | archive_issue, delete_issue |
| Dependencies | list_issue_dependencies, add_issue_dependency, remove_issue_dependency |
| Labels and workflow | list_workflow_states, list_issue_labels, create_label, add_issue_label, remove_issue_label |
| Teams and people | list_teams, get_team, list_users |
| Projects | create_project, get_project, list_projects, list_project_issues, set_issue_project, remove_issue_from_project, update_project, update_project_details, archive_project |
| Project labels | list_project_labels, create_project_label, add_project_label, remove_project_label |
| Project updates | create_project_update, list_project_updates |
| Cycles | create_cycle, update_cycle, archive_cycle, list_cycles, list_cycle_issues |
Search and list tools accept limit and cursor. Their responses keep the same shape:
{
"items": [], "next_cursor": null }
Pass a non-null next_cursor back as cursor to request the next page.
list_issue_dependencies returns separate blocks and blocked_by lists. Each item includes its relation_id; use it to remove that dependency. Its next_cursors object has separate cursors for each direction.
archive_issue, archive_project, and delete_issue are marked with MCP's destructiveHint. They refuse to call Linear until the client invokes them with confirm=true.
Deletion requires explicit confirmation: set confirm=true
This prevents an accidental tool call from deleting or archiving data. It does not replace Linear's own access controls: the API key still determines which resources the server may read or change.
.venv/bin/ruff check .
.venv/bin/python -m pytest
The current checkout produces:
All checks passed!
.......... [100%] 10 passed
The tests cover pagination bounds and response shape, authenticated-user issue resolution, project membership, cycle queries, dependency direction, confirmation guards, cycle lifecycle operations, and MCP tool registration. GitHub Actions runs the same lint and test commands on Python 3.10, 3.11, 3.12, and 3.13.
Abscissa is a local stdio server, not an HTTP service. It needs a running MCP-capable client and a valid Linear API key. The automated suite avoids mutating a real Linear workspace; create, update, archive, and delete behavior is therefore protected by unit tests rather than a live write test.
MIT