Linear is the issue tracker for modern product and engineering teams. AllMCP provides 100 tools across 23 categories — issues, projects, cycles, initiatives, teams, users, labels, comments, documents, customers and more — behind a single endpoint.
Linear connects with a personal API key that you create inside your own Linear workspace. There is no OAuth screen and nothing to re-authorize on a schedule — the key does not expire until you revoke it.
Create a personal API key
In Linear, go to Settings → Security & access → Personal API keys (or open linear.app/settings/account/security, which redirects to your own workspace), click New key, name it something like “AllMCP”, and copy the value. Linear shows the key once.
Open the secure key-entry page
Ask your agent to connect Linear. It replies with a browser link to the AllMCP key-entry page — the agent never sees or handles the key itself. Paste the key there. One field is required:
API key — the value you copied above.
Start asking for work
Once the key is saved, the Linear tools are live on your existing AllMCP endpoint. Nothing else to install.
Once Linear is connected, your agent can use the tools below. You never call them by name — describe the outcome you want in plain language and the agent picks the tools and resolves the IDs.
Seven categories are available the moment you connect — issues, users, teams, projects, comments, search and labels — which is where the large majority of day-to-day work happens. The remaining sixteen become available as soon as a request needs them.
Lists issues, filtered by team, assignee, workflow state, project, cycle, label, priority or a title substring, sorted by last update or creation date.
linear_get_issue
Retrieves one issue in full — by its ID or its human identifier such as ENG-123 — including description, creator, subscribers and sub-issues.
linear_create_issue
Creates an issue in a team, optionally with a Markdown description, assignee, starting status, priority, estimate, project, cycle, labels, parent issue and due date.
linear_update_issue
Changes an issue’s title, description, assignee, status, priority, estimate, project, cycle, labels, parent or due date.
linear_archive_issue
Archives an issue. Reversible — Linear keeps archived issues.
linear_delete_issue
Permanently deletes an issue. Requires an explicit confirmation, and archiving is offered first.
Fuzzy, ranked search across issues, projects or documents by name or phrase — how the agent finds the thing you described when you did not give it an ID.
Attaches an external URL — a pull request, a Figma file, a monitoring alert — to an issue, with an optional display title. Linking the same URL twice updates the existing link instead of duplicating it.
linear_update_attachment
Changes an attachment’s title or subtitle.
linear_delete_attachment
Removes an attachment from an issue. Requires confirmation.
You speak in names, the agent works in IDs. Linear identifies teams, people, statuses and labels by internal ID, so the agent looks each one up before it writes. That means “assign it to Marina” works — but a name that matches several members will make the agent ask which one you meant rather than guess.
Statuses belong to teams. Each team names its own workflow states, so “Done” in one team is a different status from “Done” in another. Ask about a status in the context of its team.
Priority is a fixed five-step scale — no priority, urgent, high, medium, low — the same one you see in the Linear app.
Archiving is the safe default; deleting is not. Issues, projects, cycles, initiatives and roadmaps can be archived and brought back. Permanent deletes — of issues, comments, labels, documents, milestones, views, customers and releases — always require an explicit confirmation first.
Customers and Releases need to be enabled for your workspace. If those features are off, those tools report a permission error rather than returning empty results. Roadmaps are Linear’s legacy feature — prefer initiatives for new work.
Search covers titles and descriptions, not comment threads. If something was only ever said in a comment, ask the agent to open the issue and read its comments.
Descriptions, comments, documents and status updates are Markdown, and an update replaces the existing body rather than appending to it. Ask the agent to read the current text back before it rewrites anything long.
Linear rate-limits personal API keys to roughly 1,500 requests per hour, so very large sweeps are paged through steadily. If you hit the ceiling, the agent tells you and backs off rather than hammering the API.
Webhooks and account-security operations are deliberately not included. AllMCP will not create or revoke Linear API keys, OAuth apps or sessions on your behalf, and it does not subscribe to Linear events — set those up directly in Linear if you need them.
