Linear MCP
Another Linear MCP Server
Quickstart
1. Get Linear API Key
Obtain a Linear API Key from your Linear Account: https://linear.app/YOUR-ORG-NAME-HERE/settings/account/security
2. Install pipx
# MacOS
brew install pipx
# Linux
apt install pipx
# (All environments) Set up PATH
pipx ensurepath
Cursor
Create a command MCP server with the following command:
pipx run linear-mcp --linear-api-key ... --team_name ...
Windsurf
In Windsurf settings, add a Custom MCP server with configuration like the following:
{
"mcpServers": {
"linear": {
"command": "pipx",
"args": [
"run",
"linear-mcp",
"--linear-api-key",
"...",
"--team_name",
"..."
]
}
}
}
Development
Using Docker
# Build the image
docker build -t linear-mcp .
# Run the container
docker run -it --rm -e LINEAR_API_KEY=... linear-mcp LINEAR_TEAM_NAME=...
Using pipx
To build the pipx package locally, run:
pipx install -e . --force
Using Virtual Environments
- Create and activate a virtual environment:
python -m venv venv
source venv/bin/activate # On Windows: venv\Scripts\activate
- Install build dependencies:
pip install -r requirements-build.txt
- Install development dependencies:
pip install -r requirements-dev.txt
- Install the package in development mode:
pip install -e .
Releases
This repository is published to PyPI using GitHub Actions.
This happens automatically when you push to the main branch.
If you do not bump the verison in pyproject.toml, the release will fail.
Prior to merging to main, it is also a good idea to install the package globally on your local machine:
pipx install -e . --force
... and then use the mcp inspector to test all the resources, tools, etc.:
npx @modelcontextprotocol/inspector linear-mcp --linear-api-key ... --team_name ...
Because a transport stdio cannot write to standard out, there is file based logging.
By default, the server writes to linear_api.log, whose location varies depending on how the server was installed / started.
License
MIT License
Metadata
Release files for linear-mcp 0.1.7
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | Provenance | |
|---|---|---|---|---|
| linear_mcp-0.1.7.tar.gz | 10.0 kB | Without provenance | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| linear_mcp-0.1.7-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 19.8 kB
Release files / linear_mcp-0.1.7.tar.gz
| Download URL | linear_mcp-0.1.7.tar.gz |
|---|---|
| Size | 10.0 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
5570ee96f633aff832227b69d86b80b0e3e267bfc6c4aca8257c7fa5a76dcc59
|
|
BLAKE2b-256 checksum How to use checksums |
0e15d28f6c6cea561171dc22dc8e7301afe3c0ab75cbfba88f526c3931620bef
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Release files / linear_mcp-0.1.7-py3-none-any.whl
| Download URL | linear_mcp-0.1.7-py3-none-any.whl |
|---|---|
| Size | 9.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
643cf6a23c2b2aa54345518674b6875a8afb1a2f172ec1205063aa2e0e5dc392
|
|
BLAKE2b-256 checksum How to use checksums |
3da15f951f8c03755f2282ad3d8605646d6ddf0de39dee0ebb641e00a65e9c25
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
No |
| Uploaded via |
twine/6.1.0 CPython/3.12.9
|
Security for linear-mcp 0.1.7
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
No provenance found
None of the files in this release were uploaded with provenance metadata.
A note on package security
PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.
To learn more about protecting yourself from malicious actors, visit our package security documentation.