Share Linear MCP tools.
Issues, projects, and cycles for remote teammates — writes need your approval.
Run on your machine
Start the server on your host machine. Tools not listed in --allow are completely hidden from the agent.
npx -y @mcpwire/cli share \
--name linear \
--allow "linear_get_issue,linear_search_issues,linear_search_issues_by_identifier,linear_get_teams,linear_get_user,linear_list_projects,linear_get_project,linear_get_project_milestones" \
--redact-secrets \
-- npx -y mcp-server-linear@1.6.0
Exposes 8 default tools with pattern-based secret redaction.
Optionally set an expiry with --ttl 30m, prompt for approvals with --confirm, or limit calls with --max-calls 20.
Connect your teammate’s agent
MCPWire prints a unique wire://... ticket in your terminal. Send it privately to your teammate to paste into their MCP client:
{
"mcpServers": {
"linear": {
"command": "npx",
"args": [
"-y",
"@mcpwire/cli",
"join",
"wire://<TICKET_FROM_HOST>"
]
}
}
}
Replace <TICKET_FROM_HOST> with the active session ticket. The agent can only discover and call the tools exposed above.
Scoped tool permissions
MCPWire acts as a Layer 7 JSON-RPC firewall. Requests for blocked tools are dropped on the wire before ever touching your machine.
| Tool | Default Policy | Notes |
|---|---|---|
linear_get_issue | Allowed | Reads an issue by ID. |
linear_search_issues | Allowed | Searches issues with filters. |
linear_search_issues_by_identifier | Allowed | Reads issues by human key, e.g. ENG-123. |
linear_get_teams | Allowed | Lists teams. |
linear_get_user | Allowed | Reads a user profile. |
linear_list_projects | Allowed | Lists projects. |
linear_get_project | Allowed | Reads project details. |
linear_get_project_milestones | Allowed | Lists project milestones. |
linear_create_issue | Blocked (High risk) | Creates issues. |
linear_create_issues | Blocked (High risk) | Creates issues in bulk. |
linear_edit_issue | Blocked (High risk) | Updates issue fields, status, and assignees. |
linear_bulk_update_issues | Blocked (High risk) | Updates many issues at once. |
linear_delete_issue | Blocked (High risk) | Deletes issues. |
linear_create_comment | Blocked (High risk) | Posts comments as your identity. |
linear_update_comment | Blocked (High risk) | Edits comments. |
linear_delete_comment | Blocked (High risk) | Deletes comments. |
linear_resolve_comment | Blocked (High risk) | Resolves comment threads. |
linear_create_project_with_issues | Blocked (High risk) | Creates projects with issues. |
linear_create_project_milestone | Blocked (High risk) | Creates milestones. |
linear_update_project_milestone | Blocked (High risk) | Updates milestones. |
linear_delete_project_milestone | Blocked (High risk) | Deletes milestones. |
linear_auth_callback | Blocked (Review) | OAuth callback helper; only relevant when authenticating interactively. |
Test and verify
Try these recommended prompts to confirm the agent receives expected outputs and that restricted actions fail safely.
Try Linear
Create a Linear API key and set LINEAR_API_KEY in the host environment. Linear ships an official MCP server, but it is remote-only and outside this catalog’s stdio support, so this entry uses the widely used community server.
Ask the agent to look up an issue with linear_search_issues_by_identifier (e.g. ENG-123), search by keyword with linear_search_issues, or summarize a project with linear_get_project. Issues, comments, and project data flow to the guest while the session is open. Every mutating tool — create, edit, bulk update, delete, comments, milestones — stays outside the default allowlist.
The generated command above contains the catalog’s explicit default allowlist. Check the guest’s tool list before making calls and use the server’s argument schema for required fields. See the CLI guide for guest configuration and session controls for approvals, redaction, and expiry.
--record session.wirelog to your host command. Drop the resulting file into the Session Replay Viewer to inspect timestamps, latency, blocked attempts, and secret scrubbing.