io.github.KazKozDev/abscissa

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.

Run it

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.

Example prompts

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.

Tools

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.

Destructive actions

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.

Verify the checkout

.venv/bin/ruff check .
.venv/bin/python -m pytest

The current checkout produces:

All checks passed!
.....

... [View full README on GitHub](https://github.com/kazkozdev/abscissa#readme)