# Linear MCP > 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. ## Overview - **Category:** loved-by-devs - **Price:** Free - **Tags:** issue-tracking, sprint-planning, workflow-automation, task-management, team-collaboration, software-development ## Description 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. ## Tools ### create_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 level. ### list_cycles Retrieves a list of all sprint cycles (sprints) for a specific team, showing dates and completion percentage. ### get_issue Pulls the full details for an issue using either its UUID or human-readable identifier like TEAM-123. ### 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 limit setting. ### search_issues Searches for issues using text input and can optionally narrow results to a single team. ### list_teams Retrieves all teams in your workspace, providing their unique IDs, names, and key prefixes. ### update_issue Changes specific fields on an existing issue using its UUID; you only provide what needs changing. ### get_viewer Checks and returns the details of the account that currently owns the API token. ## Prompt Examples **Prompt:** ``` Show me all unresolved issues assigned to the Engineering team. ``` **Response:** ``` I've queried your Engineering team and found 7 open issues. The highest priority items are 'Fix auth token refresh bug' (ENG-142) and 'Implement pagination for API responses' (ENG-138). Would you like full details on either? ``` **Prompt:** ``` Create a new issue in the Backend team titled 'Add rate limiting to /api/search endpoint' with high priority. ``` **Response:** ``` Done! I've created issue **BE-217** titled 'Add rate limiting to /api/search endpoint' with priority High in the Backend team. You can view it at linear.app/yourco/issue/BE-217. ``` **Prompt:** ``` What's the current sprint cycle progress for the Mobile team? ``` **Response:** ``` The Mobile team's active cycle is #47 (Mar 31 — Apr 13) with 62% completion. There are 14 issues in this cycle, 5 of which are already done. Would you like the list of remaining open issues? ``` ## Capabilities ### Discover teams and users The MCP retrieves authenticated user details and lists all configured development teams in your workspace. ### Search for specific issues You can search across the entire platform to find issues based on text, state, or assignee. ### Manage issue lifecycle The system allows you to create new issues, modify existing ones, and add collaboration comments directly. ### Track project timelines You can list all active projects by name or ID, view their status, and drill down into specific details. ### Inspect sprint progress The MCP lists all historical and current development cycles for any team, including completion percentage and dates. ## Use Cases ### 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. ## Benefits - 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. ## How It Works The bottom line is that you just talk to your agent; it handles all the data calls and updates for you. 1. Subscribe to this MCP on Vinkius. 2. Enter your Linear Personal API Key into the connection settings. 3. Tell your AI client what you need done, like 'Show me all high-priority issues in the Backend team.' ## Frequently Asked Questions **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.