Linear
Work with Linear issues, comments, projects and teams through Linear's own MCP tools, or run any GraphQL query or mutation. Connect with OAuth or a personal API key.
- rest
https://api.superagnt.com/v1/connections/linearplus the vendor's own path, with your superagnt_ API key asAuthorization: Bearer.- mcp
- Tools named
connection_linear_*onhttps://mcp.superagnt.com/mcp, served once the account is connected. - billing
- Linear bills your own account. Calls cost no superagnt_ data credits.
- rate limit
- 10 requests a second, 600 a minute: the vendor's ceiling as the registry records it, for sizing bursts. Your plan's own limit is on Connections.
- vendor docs
- https://developers.linear.app/docs
The Linear connection gives an agent two ways into your Linear workspace. Linear's own MCP server is built in, and its tools are shaped for agents: issues, comments, attachments, projects, milestones, initiatives, documents, cycles, teams and users. For anything they do not cover, the GraphQL operation runs any query or mutation in Linear's schema.
Linear's MCP tools
Connecting Linear also lights up its MCP server, with no URL to add. The tools are named mcp_linear_<tool>, such as mcp_linear_list_issues, mcp_linear_get_issue, mcp_linear_save_issue, mcp_linear_save_comment, mcp_linear_list_projects and mcp_linear_list_teams, and form the mcp:linear family. Linear maintains the list, so it follows Linear's server rather than this page. They use the same credential as the GraphQL operation. How remote MCP tools are named, cached and permissioned: Remote MCP servers.
01
Setup
Connect with Linear
- Start the install. In the superagnt app open Integrations, pick Linear and click Connect with Linear.
- Approve access. Linear asks for the
readandwritescopes.
Paste a personal API key
If Connect with Linear is not offered, the connect dialog opens on the key form. To use a key instead of OAuth, click Use API key instead.
- Create a key. In Linear open Settings → Account → Security & access and create a personal API key. It starts with
lin_api_. - Paste it. Paste it as the API key on the Linear connection.
When a workspace has both an OAuth install and a pasted key, calls use the OAuth install.
02
Things to know
- The GraphQL operation is one tool,
connection_linear_lineargraphql, and one REST path,POST /v1/connections/linear/graphql. Its body is the GraphQL envelope:query(required),variablesandoperationName. - The GraphQL tool runs without asking by default, mutations included, because one tool carries every query and mutation. Set it to ask, for the workspace or for one agent, when an agent should not change Linear on its own (Permissions).
- Linear's MCP tools take their default from the hints Linear publishes on each tool: a read-only tool runs, a destructive one always asks. A tool with neither hint runs when its name reads like a lookup (
get,list,search) and asks otherwise.
03
Examples
Check the connection
curl -X POST "https://api.superagnt.com/v1/connections/linear/graphql" \
-H "Authorization: Bearer $AGNTDATA_API_KEY" \
-H "Content-Type: application/json" \
-d '{"query":"query { viewer { id name email } }"}'Find your team ids
curl -X POST "https://api.superagnt.com/v1/connections/linear/graphql" \
-H "Authorization: Bearer $AGNTDATA_API_KEY" \
-H "Content-Type: application/json" \
-d '{"query":"query { teams { nodes { id key name } } }"}'Create an issue
curl -X POST "https://api.superagnt.com/v1/connections/linear/graphql" \
-H "Authorization: Bearer $AGNTDATA_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"query": "mutation ($input: IssueCreateInput!) { issueCreate(input: $input) { success issue { id identifier url } } }",
"variables": {
"input": {
"teamId": "TEAM_ID",
"title": "Investigate flaky deploy",
"description": "See the ops thread from this morning."
}
}
}'04
Receiving Linear webhooks
This connection calls Linear; it does not receive Linear's events. To trigger an agent from Linear, create an inbound endpoint in the superagnt app (Webhooks, the Inbound tab, Create Webhook), copy its URL, and add it as a webhook in Linear's settings. Linear signs deliveries with its own signature header, which an inbound endpoint does not check, so leave the endpoint's signature verification off and keep its URL secret. Binding the endpoint to an agent or a pipeline is on Receiving webhooks.
0 tools, one per resource and risk
MCP servers and agents on the grouped surface list Linear as these tools. Each takes an action, and the ones that work across record types an object. Every operation also keeps its own per-operation name, in the next table, which works on every server. How grouping works: Grouped tools.
| Tool | Risk | Actions |
|---|
All 1 operations
Each operation is a REST path under https://api.superagnt.com/v1/connections/linear and an MCP tool. The per-operation tool name is the one permissions, approvals and usage records use.
| Operation | MCP tool |
|---|---|
POST /graphqlExecute a GraphQL query or mutation | connection_linear_lineargraphqlgrouped servers list it under this name |