MCP Gateway · OpenCode
Connect Linear to OpenCode
OpenCode users can keep Linear open beside the terminal session instead of in a browser tab. The agent reads team conventions from Linear documents, labels technical debt as it finds it, and checks who owns an area before asking for review. The OpenCode plugin sends each prompt and tool call to Speakeasy, which allows or denies it.
- Category
- Project management
- Tools
- 31
- Authentication
- OAuth
- OpenCode
- Terminal
Behind the MCP Gateway
Run Linear MCP behind the MCP Gateway
One URL for every agent, sign-in through your IdP, RBAC down to the tool, and every Linear call inspected and logged.
Set up
Add Linear to OpenCode in 4 steps
- 01
Add Linear from the catalog
An admin finds Linear in the MCP Catalog (MCP Gateway > MCP > Catalog) and clicks Add. Speakeasy registers the vendor's server as a remote MCP server and proxies sessions to it. Nothing is copied or re-hosted.
Linear uses OAuth. Servers that support dynamic client registration get their OAuth configuration applied automatically.
Where MCP-scoped policies are enabled, the install offers a recommended risk policy for the new server that detects secrets and PII and inspects tool requests and responses.
- 02
Choose who can use Linear
Give teams the
mcp:connectscope on the Linear server through team access or a role. OpenCode connects to the Linear server's own URL, and the server's authorization decides who can connect and which tools they can call. - 03
Connect OpenCode
Add the server to OpenCode's own mcp config block as a remote server.
Copy the server's URL from its hosted install page in Speakeasy.
Add it to the
mcpblock of your OpenCode config withtypeset toremote.Restart OpenCode and sign in when prompted.
{ "mcp": { "<server slug>": { "type": "remote", "url": "<URL from the hosted install page>" } } } - 04
Sign in and use Linear from OpenCode
The first time OpenCode connects, it opens a browser so the person can sign in to Speakeasy through your identity provider.
Linear needs its own OAuth grant, so each person connects it once. Until they do, Linear calls fail while the rest of the gateway keeps working.
From then on, Linear's tools appear in OpenCode, limited to what the person's access allows, and every call lands in the gateway's tool logs.
OpenCode doesn't receive MCP servers from plugins. The observability package is installed separately, from a ZIP or with speakeasy-hooks install --provider=opencode, and the device agent can maintain it.
Use cases
What OpenCode users do with Linear
Read team conventions before coding
Have OpenCode find the team's engineering guidelines among Linear documents and read them first, so the code it writes follows house rules for naming and testing.
Label technical debt you uncover
When OpenCode spots a workaround or an outdated dependency, it files an issue with the team's tech debt label instead of leaving another comment in the source.
Find the right reviewer
Ask OpenCode which team owns the area you changed and who belongs to it, then leave a comment on the related issue asking them to review.
Tools
31 tools
Each Linear tool can be allowed or denied per team and role at the MCP Gateway before OpenCode sees it.
get_attachment
Retrieve an attachment's content by ID.
create_attachment
Create a new attachment on a specific Linear issue by uploading base64-encoded content.
delete_attachment
Delete an attachment by ID
list_comments
List comments for a specific Linear issue
save_comment
Create or update a comment on a Linear issue. If id is provided, updates the existing comment; otherwise creates a new one. When creating, issueId and body are required.
delete_comment
Delete a comment from a Linear issue
Control
What Speakeasy can see and stop in OpenCode
The gateway covers every client the same way. The rest depends on what OpenCode exposes to Speakeasy.
Tool logs
Gateway
Every Linear call is logged with the person and the client that made it.
Access by role
Gateway
People reach only the Linear tools their team or role allows.
Request and response blocking
Gateway
A risk policy scoped to Linear can reject a tool request before it reaches the server, or withhold a result from OpenCode. MCP-scoped policies are enabled per organization.
Prompt and tool-call blocking
OpenCode
The OpenCode plugin sends each prompt and tool call to Speakeasy, which allows or denies it before it runs.
Usage telemetry
OpenCode
Token and cost totals flow through the plugin, reported per turn.
Device agent
OpenCode
The device agent installs and maintains the observability package.
- OpenCode has no OpenTelemetry exporter, so session data comes through the plugin.
- Tool output is blocked at the gateway rather than in OpenCode's hooks.
Questions
Frequently asked questions
Does OpenCode report usage for Linear sessions?
Where is Linear tool output blocked for OpenCode?
How do OpenCode users get Linear?
Are Linear calls from OpenCode logged?
Connect more