Linear
Find, create and update issues, projects and comments in the workspace you choose.
A Linear connection gives a playbook's functions Linear's MCP server. You sign in to Linear, choose a workspace and allow access, and the connection acts as you in that workspace, with what your account can see.
Available on Auto Cloud and on self-hosted runtimes.
What a playbook can do with Linear
- Find issues, projects, comments, teams and the other data your account can see.
- Create and update issues and projects, and comment on them.
The server offers what Linear lists for it, and a tool that changes anything is called only by a function whose definition names it.
Linear's MCP server lists its own tools when a function runs, and once you connect, your agent lists them with list_connection_tools.
An example workflow
Customer feedback that becomes issues, without duplicates. An event trigger starts the workflow when a support playbook records a piece of feedback, or a schedule trigger runs it hourly over a Slack channel's new messages through a Slack connection. A lookup function searches Linear for issues that already describe the same thing, with the words the feedback uses. A reasoning function reads the matches with the team's rules in its prompt and decides: a comment on an existing issue, a new issue in the right team with the right labels, or nothing, because it is praise rather than a request. An interaction function creates the issue or adds the comment through the server's tools, with the customer's words quoted and the source linked. Where the reasoning function is unsure whether two reports are the same, it asks the product manager through Slack and waits. The run's history in Studio keeps every decision and the issue it led to.
How to connect Linear
- Sign in to Linear, choose a workspace and allow access. The consent screen shows the permissions listed below.
Then:
- Ask your agent to connect Linear to Auto, or open Settings, Agents, Connections in Auto Studio and choose Linear.
- On the Studio page, check the service and its access, choose which playbooks may use the connection, and approve it.
- Have your agent check one small read through the connection before a function depends on it.
What it needs
- A Linear account in the workspace; the connection has your access there.
- Your agent connected to Auto and signed in as you, with permission to change your organization, if your agent adds the connection.
- On a self-hosted runtime, nothing to register: Linear's server takes a client Auto names by its metadata document or registers itself, or one you registered.
Linear grants reading and writing as two scopes; what a function changes is what its definition names among the server's tools.
Permissions Auto asks for
- Read the issues, projects, comments, teams and other data the Linear account can see.
- Create, change, archive and delete issues, projects, comments and other data as the Linear account.
Good to know
An issue the playbook creates is created by you, so its wording carries your name in Linear; the reasoning function's prompt, which shapes the wording, is in Studio for the team to read. What a function reads is kept in the run's history, where people with access to the playbook can read it.