Connect MCP Servers to Linear Agent
Overview
Linear Agent can connect to MCP servers to access tools and data outside of Linear.
This lets the agent bring external context into your workflows to investigate issues, plan projects, write specs, and draft updates grounded in your full context.
MCP works across Linear Agent chat, comments, and automations, and is enabled at the workspace level by Admins.
Available servers
- Amplitude
- Attio
- Better Stack
- Datadog
- GitHub
- Glean
- Granola
- HubSpot
- incident.io
- Intercom
- Jam
- Notion
- PostHog
- Sentry
- Slack
- Stripe
Enable Agent MCP connections
From the Workspace Settings an Admin can:
- Enable or disable MCP support for the workspace
- Restrict usage to approved MCP servers
- Manage workspace-connected MCP servers
Enable on the Workspace
- Open Workspace settings > AI & Agents settings > Linear Agent
- Beside Enable MCP servers toggle it to “On”
- Click on Manage next to “Allowed MCP servers”
- Scroll down to MCP servers and select any that users and automations can connect to via Linear Agent


Select available servers for the workspace including any custom servers using a URL
Enable a Custom Server
- Click + Custom URL…
- Select Custom URL…
- Enter your server URL (must start with
http://orhttps://) and complete the connection flow:
- No authentication → connects immediately
- OAuth supported → sign in and authorize
Once connected, the customer server will be available for users to connect to through their settings

User MCP Connection steps
- Open Settings > Agent personalization
- Under MCP servers click on the “+” (Add server) button
- Choose a server and start the connection flow
- Complete authentication with the provider
- Return to Linear and confirm the server shows as connected

After a server is connected, users can reference it in natural language when using Linear Agent. The agent can use the connected MCP server to gather information or perform supported actions. For example:

Example prompts
- Investigate this issue using Sentry and summarize the likely cause
- Check Datadog for recent errors related to this workflow
- Look up the latest notes about this customer in Intercom
- Search Notion for relevant documents and generate a guide ahead of launch
- Use GitHub to find the pull request that likely introduced this change