Featured workflow
Engineering Sprint and Deploy Review
Engineering updates are grounded in data instead of ad-hoc Slack check-ins.
CONNECTOR
Runner uses Linear through a native MCP server with guidance for issue management, sprint cycles, status tracking, and cross-team visibility.
The app page is only useful if it shows how Linear fits into a real job. This preview is pulled from the live workflow pages that already use the connector.
Featured workflow
Engineering updates are grounded in data instead of ad-hoc Slack check-ins.
Connected apps
Why it's better
Common pairings
Public workflow pages where Linear is part of the connected stack.
These examples are grounded in the real Runner backend connector definitions and connector guidance docs, not generic marketing filler.
Linear
"Show me open issues assigned to the platform team in this sprint cycle."
Runner surfaces engineering work without pulling unfiltered backlogs.
Linear
"Create a Linear issue for the auth bug Maya flagged, assign to platform, and link it to the security project."
Action items from meetings become tracked engineering work without context switching.
Linear
"Show the current cycle progress and any blocked issues before the engineering sync."
Sprint health becomes part of the operating context before the meeting.
Linear
"Mark the auth fix as Done and add a comment with the deploy confirmation."
Issue state stays current without switching to Linear.
Linear
linear_link_issues
Create blocks, blockedBy, or relatedTo relationships between issues.
"Link the API migration issue to the three frontend tasks it blocks."
Cross-team dependencies become visible instead of living in Slack threads.
Provider
Category: Project Management.
Backend
Backed by the Linear MCP server at `https://mcp.linear.app/mcp`, with connector guidance for issue filtering, status management, and sprint tracking.
Operational note
Never call list_issues unfiltered — workspaces grow large fast. Always scope by team, project, or assignee.
Operational note
Status names are team-specific; call list_issue_statuses(team) before using.
Testimonials
The value is the same across connectors: real context in, real work out, no copy-paste operating model.
“I got hours back every week. Runner handles the follow-through work that used to sit open across tabs and docs.”
“It gives me one place to work across email, calendar, and docs. The time savings are real.”
“I stopped losing deals to slow follow-up. Runner drafts the reply and schedules the next step before I forget.”
“Runner connects my CRM, email, and meeting notes so I actually prep for calls instead of winging it.”
“What used to take half a day now takes one focused pass in the morning.”
“Meeting follow-up used to die in my notebook. Now the recap, emails, and calendar items happen before I leave the room.”
“I tried every productivity tool on the market. Runner is the first one that actually finishes work instead of just organizing it.”
“Board prep went from a full Sunday to a one-hour Monday morning workflow. The context is already assembled.”
“The morning briefing workflow changed how I start every day. I see blockers, priority threads, and follow-ups before the first meeting.”
“The double opt-in intro workflow is the single most useful thing I have run this quarter. Warm intros used to take 20 minutes each.”
“Investor updates that used to take a full day now come together in 45 minutes from real data.”
Download Runner to connect Linear to the rest of your workflow instead of treating it like another isolated tab.