Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"linear-mcp-2","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# 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` ```bash # 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: ```bash pipx run linear-mcp --linear-api-key ... --team_name ... ``` ### Windsurf In Windsurf settings, add a Custom MCP server with configuration like the following: ```json { "mcpServers": { "linear": { "command": "pipx", "args": [ "run", "linear-mcp", "--linear-api-key", "...", "--team_name", "..." ] } } } ``` ## Development ### Using Docker ```bash # 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: ```bash pipx install -e . --force ``` ### Using Virtual Environments 1. Create and activate a virtual environment: ```bash python -m venv venv source venv/bin/activate # On Windows: venv\Scripts\activate ``` 2. Install build dependencies: ```bash pip install -r requirements-build.txt ``` 3. Install development dependencies: ```bash pip install -r requirements-dev.txt ``` 4. Install the package in development mode: ```bash 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: ```bash pipx install -e . --force ``` ... and then use the mcp inspector to test all the resources, tools, etc.: ```bash npx @modelcontextprotocol/inspector linear-mcp --line…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.