# Linear MCP MCP Server > **Linear MCP MCP Server** is a hosted, multitenant Model Context Protocol (MCP) server run by **MewCP** (https://mewcp.com), giving AI agents managed access to Linear MCP. > > MewCP takes care of all MCP infrastructure for you — credential storage, OAuth flows, > token refresh, and production-grade auto-scaling — so your AI agents can connect to > third-party services and run freely without you managing any MCP server yourself. > > Server page: https://mewcp.com/mcp/linear-mcp > MewCP docs: https://docs.mewcp.com > Full catalog: https://mewcp.com/llms.txt --- ## About Linear is a project management and issue-tracking platform used by software and product teams. Its MCP server enables AI assistants to search, create, and update issues, projects, and other work-management objects directly through natural language. --- ## Details - Server ID: `linear-mcp` - Version: 1.0.0 - Tools: 67 - Authentication: OAuth, managed by MewCP - Transport: http --- ## Access The gateway URL below serves your **entire MewCP toolset**, not this server on its own. Pasting a config snippet is not enough — Linear MCP has to be in the toolset first. In order: 1. Add Linear MCP to your toolset at https://mewcp.com/mcp/linear-mcp 2. Connect your Linear MCP account (OAuth); MewCP stores the credential and attaches it to each call 3. Copy your MewCP API key from the dashboard (Developer) 4. Configure your client with the snippet for it below Once connected, an agent does **not** see this server's tools as top-level tools. It sees four meta-tools and reaches everything through them: - `search(query)` — find tools by keyword across the toolset - `get_schema(tools)` — full description and arguments for the tools you picked - `list_accounts(provider)` — only when one app has several connected accounts - `call_tool(server_maskedId, tool_name, args)` — execute So the list below is what `search` can return for this server, not a set of callable tool names on their own. --- ## Tools (67) Descriptions are truncated to 160 characters; call `get_schema` for the full text and the argument schema. Where a tool is annotated, its type is shown — treat `destructive` as irreversible. - `get_attachment` _(read)_ — Retrieve an issue attachment by ID. Use format=url to get its title and download URL without fetching the file content. Linear upload URLs are signed for five… - `prepare_attachment_upload` _(write)_ — Prepare a direct Linear file upload for an existing issue. Workflow: 1. Call this tool with issue, filename, contentType, and size. 2. Upload raw bytes with… - `create_attachment_from_upload` _(write)_ — Link an already-uploaded Linear assetUrl to an existing issue as an attachment. Use this only after: 1. prepare_attachment_upload returned an assetUrl and… - `create_attachment` _(write)_ — Deprecated fallback for tiny files only. Accepts base64 file content, verifies SHA-256 checksum, and uploads it through the MCP worker. Prefer… - `delete_attachment` _(destructive)_ — Delete an attachment by ID - `list_agent_skills` _(read)_ — List Linear Agent skills available to the authenticated user. - `get_agent_skill` _(read)_ — Retrieve a Linear Agent skill by ID, including its full markdown instructions. - `list_comments` _(read)_ — List comments on a Linear issue, project, initiative, document, project milestone, or project/initiative status update. Provide exactly one of `issueId`,… - `save_comment` _(destructive)_ — Create or update a comment on a Linear issue, project, initiative, document, project milestone, or project/initiative status update. If `id` is provided,… - `delete_comment` _(destructive)_ — Delete a Linear comment. Inline description comments (those with non-null `quotedText`) anchor a mark in the editor, so their root cannot be deleted — delete… - `list_cycles` _(read)_ — Retrieve cycles for a specific Linear team - `list_custom_views` _(read)_ — Find saved issue, project, and initiative views accessible to the user, including personal, workspace, and team views. Excludes archived views and views scoped… - `get_document` _(read)_ — Retrieve a Linear document by ID or slug - `list_documents` _(read)_ — List documents in the user's Linear workspace - `save_document` _(destructive)_ — Create or update a Linear document. If `id` is provided, edits the existing document; otherwise creates a new one. When creating, `title` is required and… - `extract_images` _(read)_ — Extract and fetch images from markdown content. Use this to view screenshots, diagrams, or other images embedded in Linear issues, comments, or documents. Pass… - `get_issue` _(read)_ — Retrieve detailed information about an issue by ID, including attachments, git branch name, and active Triage Intelligence suggestions when the issue is in… - `list_issues` _(read)_ — List issues in the user's Linear workspace, including active Triage Intelligence suggestions for issues in triage. For my issues, use "me" as the assignee. Use… - `save_issue` _(destructive)_ — Create or update a Linear issue. If `id` is provided, updates the existing issue; otherwise creates a new one. When creating, `team` is required, and `title`… - `list_issue_statuses` _(read)_ — List available issue statuses in a Linear team - `get_issue_status` _(read)_ — Retrieve detailed information about an issue status in Linear by name or ID - `list_issue_labels` _(read)_ — List available issue labels in a Linear workspace or team. A retired label carries `retiredAt` and cannot be applied to new issues. - `save_issue_label` _(destructive)_ — Create or update a Linear issue label. If `id` is provided, updates the existing label; otherwise creates a new one. When creating, `name` is required. - `create_issue_label` _(write)_ — Create a new Linear issue label. Deprecated: use `save_issue_label`, which can also update labels. - `retire_issue_label` _(destructive)_ — Retire a Linear issue label so it cannot be applied to new issues. The label stays visible on issues that already have it. Retiring a label group also retires… - `restore_issue_label` _(destructive)_ — Restore a retired Linear issue label, making it available for use on issues again. Restoring a label group also restores every child label, including any that… - `list_projects` _(read)_ — List projects in the user's Linear workspace - `get_project` _(read)_ — Retrieve details of a specific project in Linear - `save_project` _(destructive)_ — Create or update a Linear project. If `id` is provided, updates the existing project; otherwise creates a new one. When creating, `name` and at least one team… - `list_project_labels` _(read)_ — List available project labels in a Linear workspace or team. Returns workspace labels by default; pass `team` to also include that team's labels. A team-scoped… - `retire_project_label` _(destructive)_ — Retire a Linear project label so it cannot be applied to new projects. The label stays visible on projects that already have it. Retiring a label group also… - `restore_project_label` _(destructive)_ — Restore a retired Linear project label, making it available for use on projects again. Restoring a label group also restores every child label, including any… - `save_project_label` _(destructive)_ — Create or update a Linear project label. If `id` is provided, updates the existing label; otherwise creates a new one. When creating, `name` is required. - `list_release_pipelines` _(read)_ — List release pipelines in the workspace. - `list_releases` _(read)_ — List releases in the workspace, with optional filtering by pipeline, stage, version, and text. - `get_release` _(read)_ — Retrieve details of a release by ID or slug. - `save_release` _(destructive)_ — Create or update a release. If `id` is provided, updates the existing release; otherwise creates a new one. When creating, `name` and `pipeline` are required.… - `list_release_notes` _(read)_ — List release notes in the workspace, optionally filtered by pipeline or covered release. - `get_release_note` _(read)_ — Retrieve release notes by ID or slug, including markdown content. - `save_release_note` _(destructive)_ — Create or update release notes. If `id` is provided, updates the existing release notes; otherwise creates a new one. When creating, `pipeline` and either… - `get_diff` _(read)_ — Exact lookup for a Linear diff. Use with review URLs, GitHub PR URLs, Linear full identifiers, UUIDs, or slugs. - `list_diffs` _(read)_ — List Linear diff pull requests visible to the authenticated user - `get_diff_threads` _(read)_ — Exact lookup for diff threads and the authenticated user's drafts. Use with review URLs, GitHub PR URLs, Linear full identifiers, UUIDs, or slugs. - `save_diff_comment` _(destructive)_ — Create, reply to, or edit a comment or persisted draft on a Linear diff. Set draft to true to save without submitting. Provide draftId to edit or submit a… - `resolve_diff_thread` _(destructive)_ — Resolve or reopen a top-level comment thread on a Linear diff - `delete_diff_comment` _(destructive)_ — Delete a comment or persisted draft from a Linear diff - `submit_diff_review` _(destructive)_ — Approve a Linear diff, request changes, or submit a review comment - `update_diff` _(destructive)_ — Update a Linear diff's title, description, reviewer requests, issue links, or status. Provide at least one update. Combined updates can partially succeed;… - `merge_diff` _(destructive)_ — Merge a Linear diff or add it to the repository's merge queue - `share_issue` _(destructive)_ — Share an issue with a workspace user who cannot otherwise access it. Use this tool only when the user explicitly asks to share the issue. - `unshare_issue` _(destructive)_ — Remove a workspace user's shared access to an issue. Use this tool only when the user explicitly asks to stop sharing the issue. - `list_milestones` _(read)_ — List all milestones in a Linear project - `get_milestone` _(read)_ — Retrieve details of a specific milestone by ID or name - `save_milestone` _(destructive)_ — Create or update a milestone in a Linear project. If `id` is provided, updates the existing milestone; otherwise creates a new one. When creating, `name` is… - `get_notifications` _(read)_ — Get a page of notifications from the authenticated user's Linear inbox. - `mark_notification` _(write)_ — Mark a Linear inbox notification as read or unread, or snooze or unsnooze it. - `list_teams` _(read)_ — List teams in the user's Linear workspace - `get_team` _(read)_ — Retrieve details of a specific Linear team - `list_templates` _(read)_ — List the Linear issue, project, and document templates available to the authenticated user. Use this to find the template a team expects, then call… - `get_template` _(read)_ — Retrieve a Linear template by ID or name: the content it pre-fills, the ids it applies, its sub-issues, and its form fields. Pass the template to save_issue or… - `list_users` _(read)_ — Retrieve users in the Linear workspace - `get_user` _(read)_ — Retrieve details of a specific Linear user - `get_workspace` _(read)_ — Retrieve the connected Linear workspace - `search_documentation` _(read)_ — Search Linear's documentation to learn about features and usage - `get_status_updates` _(read)_ — List or get project/initiative status updates. Pass `id` to get a specific update, or filter to list. - `save_status_update` _(destructive)_ — Create or update a project/initiative status update. Omit `id` to create, provide `id` to update. - `delete_status_update` _(destructive)_ — Delete (archive) a project or initiative status update. --- ## Connect Gateway URL: https://gateway.mewcp.com/personal/mcp Every request carries one header: Authorization: Bearer Replace `API_KEY` with your own key from the dashboard (Developer). ## Apps ### Claude Desktop Mac & Windows app - macOS: `~/Library/Application Support/Claude/claude_desktop_config.json` - Windows: `%APPDATA%\Claude\claude_desktop_config.json` ```json { "mcpServers": { "mewcp": { "command": "npx", "args": [ "-y", "mcp-remote@latest", "https://gateway.mewcp.com/personal/mcp", "--header", "Authorization: Bearer API_KEY" ] } } } ``` Already have an "mcpServers" section in your config? Just add the server entry inside it. 1. Open Claude Desktop → Settings → Developer → "Edit Config" 2. Paste the snippet inside the outer { } of the config file (merge with your existing "mcpServers" section if you have one) 3. Save the file and restart Claude Desktop 4. Start a new conversation — your tool will be available ### VS Code Copilot / Cline - Command Palette → "MCP: Open User Configuration" (opens mcp.json). For one project only, use .vscode/mcp.json instead. ```json { "mcp.servers": { "mewcp": { "type": "http", "url": "https://gateway.mewcp.com/personal/mcp", "headers": { "Authorization": "Bearer API_KEY" } } } } ``` Already have a "servers" section in your mcp.json? Just add the server entry inside it. 1. Open VS Code → Command Palette (Cmd+Shift+P / Ctrl+Shift+P) 2. Run "MCP: Open User Configuration" to open your mcp.json 3. Paste the snippet and save 4. Start the server when prompted (or from the MCP servers view) and use it in Copilot Chat ### Cursor AI-first editor - macOS: `~/.cursor/mcp.json` - Windows: `%USERPROFILE%\.cursor\mcp.json` ```json { "mcpServers": { "mewcp": { "url": "https://gateway.mewcp.com/personal/mcp", "headers": { "Authorization": "Bearer API_KEY" } } } } ``` Already have an "mcpServers" section in your mcp.json? Just add the server entry inside it. 1. Open Cursor → Settings → Cursor Settings → MCP 2. Click "Add new global MCP server" 3. Paste the snippet and save 4. Restart Cursor ### Codex OpenAI's CLI agent - Add the snippet to your Codex MCP config or your standard MCP config file for the CLI tool you use. ```json { "mcpServers": { "mewcp": { "type": "http", "url": "https://gateway.mewcp.com/personal/mcp", "headers": { "Authorization": "Bearer API_KEY" } } } } ``` Codex generally reads a standard MCP server block, so you can add this alongside your other configured servers. 1. Open your Codex MCP config or project-level config file 2. Paste the MewCP server block inside the config JSON/TOML structure your tool expects 3. Save the file and restart Codex 4. Verify the tool is available inside a fresh session ### Claude Code Anthropic's CLI agent - ~/.claude.json (user scope) or .mcp.json in your project root — create it if it doesn't exist. Or skip the file and use the CLI command below. ```json { "mcpServers": { "mewcp": { "type": "http", "url": "https://gateway.mewcp.com/personal/mcp", "headers": { "Authorization": "Bearer API_KEY" } } } } ``` Already have an "mcpServers" section in your config? Just add the server entry inside it. 1. Open ~/.claude.json (or .mcp.json in your project root) in a text editor 2. Paste the snippet inside the outer { } (merge with your existing "mcpServers" section if you have one) 3. Save the file and start (or restart) Claude Code 4. Or skip the file entirely and run the CLI command below instead ### OpenCode Open-source terminal agent - ~/.config/opencode/opencode.json (global) or opencode.json in your project root — create it if it doesn't exist. ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "mewcp": { "type": "remote", "url": "https://gateway.mewcp.com/personal/mcp", "enabled": true, "headers": { "Authorization": "Bearer API_KEY" } } } } ``` Already have an "mcp" section in your opencode.json? Just add the server entry inside it. 1. Open ~/.config/opencode/opencode.json (or opencode.json in your project root) in a text editor 2. Paste the snippet inside the outer { } (merge with your existing "mcp" section if you have one) 3. Save the file and start (or restart) OpenCode ### OpenClaw Self-hosted agent gateway - ~/.openclaw/openclaw.json — create it if it doesn't exist. ```json { "mcp": { "servers": { "mewcp": { "transport": "streamable-http", "url": "https://gateway.mewcp.com/personal/mcp", "enabled": true, "headers": { "Authorization": "Bearer API_KEY" } } } } } ``` Already have an "mcp" section in your openclaw.json? Just add the server entry inside "servers". 1. Open ~/.openclaw/openclaw.json in a text editor 2. Paste the snippet inside the outer { } (merge with your existing "mcp" section if you have one) 3. Save the file and restart OpenClaw ### Antigravity Google's agentic IDE - ~/.gemini/config/mcp_config.json (global) or .agents/mcp_config.json (workspace-local) — create it if it doesn't exist. ```json { "mcpServers": { "mewcp": { "serverUrl": "https://gateway.mewcp.com/personal/mcp", "headers": { "Authorization": "Bearer API_KEY" } } } } ``` Already have an "mcpServers" section in your config? Just add the server entry inside it. Remote servers must use the "serverUrl" field — the legacy "url"/"httpUrl" fields aren't supported. 1. In the editor's agent side panel, click "…" → "MCP Servers" → "Manage MCP Servers" → "View raw config" (Antigravity CLI: type /mcp instead to open the Interactive MCP Manager) 2. Paste the snippet inside the outer { } (merge with your existing "mcpServers" section if you have one) 3. Save the file — the server connects automatically ### Hermes Nous Research's CLI agent - config.yaml in your Hermes config directory (~/.hermes) — add this under a top-level "mcp_servers:" key. ```yaml mcp_servers: mewcp: url: "https://gateway.mewcp.com/personal/mcp" headers: Authorization: "Bearer API_KEY" ``` Already have an "mcp_servers" section in your config.yaml? Just add the server entry inside it. 1. Open config.yaml in your Hermes config directory 2. Paste the snippet under the top-level "mcp_servers:" key (merge with existing entries if you have any) 3. Save the file, then run /reload-mcp in Hermes (or start a fresh session) 4. Ask Hermes "Tell me which MCP-backed tools are available right now" to confirm it connected ### DeepSeek Harness DeepSeek's agent harness - cordis.yml in your DSH project — or the patch file you mount plugins from. ```yaml - id: mcp-mewcp name: '@deepseek-ai/dsh-mcp-client' config: serverName: mewcp transport: streamable-http url: https://gateway.mewcp.com/personal/mcp headers: Authorization: "Bearer API_KEY" ``` One plugin instance = one MCP server. Add this entry to your plugin list; don't nest it inside another entry. 1. Open cordis.yml (or your patch file) in your DSH project 2. Paste the entry into your plugin list, keeping the leading dash and indentation 3. Restart DSH (or let HMR reload) — tools register as mcp__mewcp__ 4. Verify with: dsh web --dump-config | grep -A3 mcp ## SDKs ### Python fastmcp client ```python import asyncio from fastmcp import Client from fastmcp.client.transports import StreamableHttpTransport SERVER_URL = "https://gateway.mewcp.com/personal/mcp" API_KEY = "API_KEY" transport = StreamableHttpTransport( url=SERVER_URL, headers={ "Authorization": f"Bearer {API_KEY}", } ) async def main(): client = Client(transport) async with client: tools = await client.list_tools() print(tools) asyncio.run(main()) ``` 1. Install fastmcp: pip install fastmcp 2. Copy the snippet into your project 3. Replace API_KEY with your key from the dashboard 4. Run your script ### TypeScript MCP SDK ```typescript import { Client } from "@modelcontextprotocol/sdk/client/index.js"; import { StreamableHTTPClientTransport } from "@modelcontextprotocol/sdk/client/streamableHttp.js"; const SERVER_URL = "https://gateway.mewcp.com/personal/mcp"; const API_KEY = "API_KEY"; const transport = new StreamableHTTPClientTransport(new URL(SERVER_URL), { requestInit: { headers: { Authorization: `Bearer ${API_KEY}`, }, }, }); const client = new Client({ name: "mewcp-client", version: "1.0.0" }); await client.connect(transport); const tools = await client.listTools(); console.log(tools.tools.map((t) => t.name)); ``` 1. Install: npm install @modelcontextprotocol/sdk 2. Copy the snippet into your project 3. Replace API_KEY with your key from the dashboard 4. Run with Node 18+ as an ES module (e.g. npx tsx script.ts)