Searches issues, files new ones with attachments, updates state, labels, and assignees, and maintains projects and milestones.
32actions available
Every action runs live through MCP. Nothing to build, nothing to maintain.
Ayro creates a new issue in a Linear team's project, filling in the title and any other details available. A bug or request becomes a tracked ticket instead of a message lost in chat.
Ayro retrieves a Linear issue's full details, including its state, assignee, and comments. Whoever's asking gets an instant status update without opening Linear.
Ayro updates an existing Linear issue's state, assignee, or other fields on request. A ticket stays current without an engineer stopping to update it manually.
Each card is one request a support team gets, and the Linear actions Ayro runs to close it.
Ayro searches Linear for an existing issue matching the report, reads the one it finds, and checks what the team is carrying in the current cycle, so a duplicate is not filed.
Ayro creates the issue in the reporter's own words, attaches the conversation or file behind it, and adds the comment that gives an engineer the context they need to start.
Ayro moves an issue into the right state, adjusts its labels, and links it to the issue it blocks or duplicates, so the board reflects what is actually happening.
Ayro sets up the project and the milestone it is working toward, and posts the project update that tells stakeholders where things stand without anyone chasing.
How it works
Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Ayro reads the Linear actions it has and picks the ones a request needs.
Authorize the Linear account your team already uses — one consent screen, no API keys, no mapping tables. Ayro can only do what you granted that account, and you can disconnect it at any time.
Describe the job the way you would hand it to a teammate. Ayro maps it to the Linear actions that close it and chains as many as the request needs.
The agent runs the actions inside the conversation the customer is already in, so nobody copies data between tabs and your team can take over at any point.
Get started freeLinear · Ayro
What can you do in Linear without me setting anything up?
These, right away:
Great, let's start with the first one.
FAQ
Setup, permissions, and the limits of what Ayro can do inside Linear.
It reads them first. Get Create Issue Default Params returns the defaults for creating an issue, List Linear States returns the workflow states that team actually uses, and Get Labels and Get Teams cover the rest, so an issue is created valid instead of landing in a state nobody triages.
All 32 actions your agent can call on Linear, straight from the live MCP connection.
Creates a new attachment and associates it with a specific, existing Linear issue.
Add a reaction to an existing Linear comment.
Creates a new comment on a specified Linear issue.
Creates a new issue in a specified Linear project and team, requiring team_id and title, and allowing optional properties like description, assignee, state, priority, cycle, and due date.
Create a relationship between two Linear issues using the issueRelationCreate mutation.
Creates a new label in Linear for a specified team, used to categorize and organize issues.
Creates a new Linear project with specified name and team associations.
Create a project milestone in Linear with a name and optional target date and sort order.
Create a project status update post for a Linear project.
Archives an existing Linear issue by its ID, which is Linear's standard way of deleting issues; the operation is idempotent.
Downloads a specific attachment from a Linear issue; the file_name must include the correct file extension.
Gets the currently authenticated user's ID, name, email, and other profile information — this is the account behind the API token, which may be a bot or service account rather than a human user.
Retrieves all cycles for a specified Linear team ID; cycles are time-boxed work periods (like sprints).
Fetches a Linear team's default issue estimate and state, useful for pre-filling new issue forms.
Retrieves an existing Linear issue's comprehensive details, including id, identifier, title, description, timestamps, state, team, creator, attachments, comments (with user info and timestamps, use issue.comments.nodes for comment IDs), subscribers, and due date.
Retrieves a single Linear project by its unique identifier.
List issue drafts.
List all issues for a specific Linear team, scoped by team ID.
Retrieves all cycles (time-boxed sprint iterations) org-wide from the Linear account; no filters applied.
Lists non-archived Linear issues; if project_id is not specified, issues from all accessible projects are returned.
Retrieves labels from Linear.
Retrieves all projects from the Linear account.
Retrieves all workflow states for a specified team in Linear, representing the stages an issue progresses through in that team's workflow.
Retrieves all teams with their members and projects.
Lists all workspace users (not team-scoped) with their IDs, names, emails, and active status.
Removes a specified label from an existing Linear issue using their IDs; successful even if the label isn't on the issue.
Remove a reaction on a comment.
Execute any GraphQL query or mutation against Linear's API.
Search Linear issues using full-text search across identifier, title, and description.
Updates an existing Linear issue using its issue_id; requires at least one other attribute for modification, and all provided entity IDs (for state, assignee, labels, etc.) must be valid UUIDs — only issueId accepts key format (e.g., 'ENG-123').
Same connection, same setup. Pick the next one your team already uses.
Opens tickets, creates projects and tasks, logs expenses, and reads the invoices, estimates, and timesheets behind a client question.
Starts and stops time tracking, reports an employee's hours and active project, and creates new projects from the conversation.
Logs hours to the right project, sends estimates from a scoping conversation, raises invoices and records payments, and sets new clients up to bill.
Logs time against the right project, reports budget and utilisation, raises and emails invoices from tracked hours, and chases what has gone unpaid.
Register cardholders and users, issue cards and pull the virtual card image, provision financial accounts and counterparties, and mint API keys.
Pulls the account's project list with assigned users, budgets, dates, and archived status, so project questions are answered from live data.

Authorize the account and your agent has all 32 actions from the first conversation.
