Linear MCP for AI Agents. Manage issue tracking from any chat client.
Linear MCP connects your AI agent directly into your issue tracking workflow. Manage projects, track sprints, and handle development tasks by simply asking questions in natural language. Get full visibility on team progress without switching apps.
Give Claude and any AI agent real-world access
The MCP retrieves authenticated user details and lists all configured development teams in your workspace.
You can search across the entire platform to find issues based on text, state, or assignee.
The system allows you to create new issues, modify existing ones, and add collaboration comments directly.
You can list all active projects by name or ID, view their status, and drill down into specific details.
The MCP lists all historical and current development cycles for any team, including completion percentage and dates.
Ask an AI about this
Waiting for input…
What AI agents can do with Linear: 12 Tools for Issue Tracking
Use these twelve tools to read data about teams, projects, cycles, and individual issues, or perform actions like creating new tickets and adding comments.
Make your AI actually useful.
Add this MCP to Claude, Cursor, or Windsurf and your AI stops guessing. It gets real tools to look things up, take action, and handle the stuff you keep doing by hand.
Start using Linear MCPCreate Comment
Adds a comment to an issue using Linear's formatted text rules.
Create Issue
Generates a brand new issue, optionally setting the assignee, labels, and priority...
List Cycles
Retrieves a list of all sprint cycles (sprints) for a specific team, showing dates...
Get Issue
Pulls the full details for an issue using either its UUID or human-readable...
Get Project
Fetches detailed information about a specific Linear project.
List Issues
Lists issues, with the option to filter results to only include tickets from a specific team.
List Labels
Displays all issue labels used across teams, including their names and colors.
List Projects
Gets a list of projects that group issues across multiple teams, with an optional...
Search Issues
Searches for issues using text input and can optionally narrow results to a single...
List Teams
Retrieves all teams in your workspace, providing their unique IDs, names, and key...
Update Issue
Changes specific fields on an existing issue using its UUID; you only provide what...
Get Viewer
Checks and returns the details of the account that currently owns the API token.
Security and governance baked right in.
Pick your AI client below to get set up. Just create a Vinkius account, subscribe, and you're instantly up and running. We handle the entire backend infrastructure, delivering out-of-the-box support for HTTPS Streamable, SSE, and OAuth2—zero messy routing required.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on each call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Linear, then connect any of our 5,200+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 5,200+ others, all in one place
- Add new capabilities to your AI anytime you want
- Connections are secured and governed automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog weekly
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Linear. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on each call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
The Constant Context Switch Solved with Vinkius AI Gateway
Today, updating an issue status is a chore. You have to switch from Slack to Linear, find the right ticket ID, navigate to the comments section, and manually type out your update—all while juggling multiple tabs.
With this MCP, you simply talk to your agent. It handles finding the right ticket, accessing its data, and logging the comment or status change for you, so all that conversation history is logged instantly.
Linear: Full Issue Visibility Through Your AI Agent
The ability to `list_teams` and then `get_issue` details means your agent can map out complex dependencies. It pulls in assignee names, priority levels, and labels—all the critical data points you usually have to manually verify.
You get a single, unified view of your entire development lifecycle without ever leaving your chat window. Your AI client is now an active participant in project governance.
What your AI can actually do with this
Need to know the status of a feature or check sprint completion? This MCP lets you talk to your Linear workspace through any compatible agent. Instead of copying links and jumping between tabs, you just ask your AI client what’s going on with a specific project or which issues are blocked.
Your agent can discover team members, list all active projects, and even pull up the full details for an issue using its ID. Want to update someone? You can add comments directly to issues right from your IDE. If you're planning out a sprint, it lists cycles with their start date, end date, and completion percentage.
Managing complex development pipelines used to mean opening Linear constantly. Now, all this data lives in the Vinkius catalog, giving your AI agent full command over your issue tracking life cycle. You get an on-demand engineering manager that works inside your existing workflow.
019d8453-d421-73dd-9e4f-c21b18b88228 Here's how it actually works
The bottom line is that you just talk to your agent; it handles all the data calls and updates for you.
Subscribe to this MCP on Vinkius.
Enter your Linear Personal API Key into the connection settings.
Tell your AI client what you need done, like 'Show me all high-priority issues in the Backend team.'
Who is this actually for?
Engineering managers, developers, and product leads who spend too much time context-switching between Jira, Slack, and Linear. It’s for anyone whose job involves tracking tickets or coordinating a software release.
They check cycle progress across multiple teams to audit sprint health without opening the native application.
They create new issues or update existing tickets and add comments directly from their IDE while coding.
They search across all projects to understand the full feature scope, identify potential roadblocks, and confirm required labels.
What Changes When You Connect
Stop context-switching. You can add comments or update issues directly through your agent, eliminating the need to open Linear just to give an update.
Get a full picture of project health by listing all active projects and checking their status without leaving your current workspace.
Track development progress instantly. Use the MCP's ability to list cycles to see sprint start/end dates and exact completion percentages.
Never lose track of a ticket again. You can search issues using search_issues across multiple teams, finding anything by title or assignee.
Simplify team discovery. Start with list_teams to get all team IDs, making it easy for your agent to target the right scope when creating new tickets.
See it in action
Need to know if a feature is blocked?
A PM asks their agent: 'What's the status of the payments module?' The agent calls search_issues and returns all relevant tickets, showing which ones are open or assigned.
The sprint just ended—what did we accomplish?
An EM asks: 'What was the completion percentage for last month's cycle?' The agent runs list_cycles and instantly reports the progress metrics, helping them audit the team's performance.
A bug report needs immediate triage.
A developer tells their agent: 'Create a new issue for the login page with High priority.' The agent uses create_issue, automatically logging it under the correct team and assigning labels.
Need to update documentation on a ticket?
An engineer asks: 'Add a note to the main API issue about the dependency change.' The agent uses create_comment right away, keeping all conversation history attached to the record.
The honest tradeoffs
What to watch out for, and the recommended way to handle each one.
Treating it like simple data retrieval
Asking your AI client simply to 'list all issues.' This is too vague and doesn't help you filter or act on the results.
Instead, use search_issues and specify criteria, like 'Show me high-priority, open issues in the Mobile team,' for actionable data.
Trying to update tickets manually
Opening a ticket, changing the assignee, then having to copy that updated information into an external report.
Use update_issue through your agent. You tell it exactly which fields to change and on what ID, and it handles the direct update.
Confusing projects with teams
Asking for 'all issues' without knowing if you mean all team-specific tickets or cross-functional project goals.
First, use list_projects to identify the scope of the project. Then, use that context when querying specific issue details.
When It Fits, When It Doesn't
Use this MCP if your primary pain point is coordinating development work or managing ticket status across multiple teams and projects. You need deep access to issue metadata (labels, priority, assignees) and cycle history. This connector excels at acting like a virtual project manager inside your chat client.
Don't use it if you just need basic communication—a general messaging tool will suffice. Don't use it if you are only tracking simple To-Do lists that don't involve formal sprints or assignees; in those cases, a lightweight task management tool might be better.
However, if your process involves structured development cycles and complex dependencies, this MCP is essential because it gives your agent the specialized tools to read cycle progress (list_cycles) and write new tickets (create_issue) with specific metadata.
Questions you might have
How does the Linear MCP handle multiple teams? +
The MCP allows you to list_teams first, giving you all team IDs and names. From there, your agent can scope its actions, ensuring issues are only listed or created within the correct team context.
Can I use the Linear MCP to find out what's happening in a sprint? +
Yes. You can run list_cycles to see all sprints for a team, including start/end dates and precise completion percentages to audit progress.
Is there an easy way to create a new issue with the Linear MCP? +
Absolutely. By using create_issue, you don't just provide a title; you can optionally set the priority, assignee, and relevant labels right from your prompt.
Do I need to know complex API IDs to use Linear MCP? +
Not really. You can start by using list_teams or list_issues to get the necessary identifiers first, and then pass those readable details back into your prompts.
What if I need to change an issue that was already created? +
You use update_issue. You only have to specify the UUID and the exact fields you want changed (like changing a label or priority), keeping it clean and targeted.
Powerful workflows you can unlock today
Find API Vulnerabilities First Using MCP
Your OpenAPI spec has 14 security findings and 3 match active HackerOne reports , your agent creates the tickets before the bounty payout
Find Codebase Duplications Using MCP Servers
Your codebase has 4 different implementations of date formatting, 3 versions of the retry logic, and 2 competing validation libraries , but nobody knows because grep only finds exact matches and these duplicates are semantic
How MCP Servers Auto-Triage Bug Reports
New bugs detected, severity classified, sprint tickets created, team notified , triage your backlog without a standup
MCP Recipe to Fix Production Crashes Faster
Your app crashed 847 times yesterday and the error report sits in Honeybadger while your Linear board has no idea , the engineer who wrote the broken code merged a different PR today
MCP Recipe to Kill Codebase Bloat
Codebase audited, bloat identified, requirements questioned, lean tickets created , kill architectural complexity before it ships
MCP Servers for Multi-Client Sprint Management
Your dev team tracks their work in Linear but the PM reports to clients in ClickUp , which means every sprint update is manually transcribed between two tools, and by the time the client sees it in ClickUp the data is already outdated