MCP Gateway · OpenCode
Connect Guru to OpenCode
New engineers ask the same onboarding questions in their first weeks, and the answers usually exist in Guru. OpenCode users can get them from the terminal by adding the server to OpenCode's mcp config as a remote entry. The OpenCode plugin sends each prompt and tool call to Speakeasy, which allows or denies it.
- Category
- Communication
- Tools
- 6
- Authentication
- OAuth
- OpenCode
- Terminal
Behind the MCP Gateway
Run Guru MCP behind the MCP Gateway
One URL for every agent, sign-in through your IdP, RBAC down to the tool, and every Guru call inspected and logged.
Set up
Add Guru to OpenCode in 4 steps
- 01
Add Guru from the catalog
An admin finds Guru 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.
Guru 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 Guru
Give teams the
mcp:connectscope on the Guru server through team access or a role. OpenCode connects to the Guru 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 Guru from OpenCode
The first time OpenCode connects, it opens a browser so the person can sign in to Speakeasy through your identity provider.
Guru needs its own OAuth grant, so each person connects it once. Until they do, Guru calls fail while the rest of the gateway keeps working.
From then on, Guru'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 Guru
Get onboarding answers from the terminal
Ask OpenCode which repositories you need, how to get database access, or who approves deploys, and get a direct answer generated from Guru's knowledge base.
Save a troubleshooting fix
After you solve a tricky build failure, have OpenCode write up the symptom and the fix and save it as a draft card for the team.
List cards about a tool
Search Guru for every card that mentions a CLI or internal service, and browse the results before deciding which one to read.
Tools
6 tools
Each Guru tool can be allowed or denied per team and role at the MCP Gateway before OpenCode sees it.
guru_answer_generation
Generate direct answers to questions using the knowledge base. Use when users ask specific questions ('What is X?', 'How do I Y?'). Provides comprehensive answers, not just documents.
guru_create_draft
Create a Draft of a Card in Guru. Use when the users ask to save the content to Guru using a Draft
guru_search_documents
Find and retrieve specific documents, sources or cards. Use when users want to discover existing content ('find me docs on X', 'do we have cards about Y'). Returns documents for browsing, not answers.
guru_update_card
Update the content of an existing card. Use when users want to modify existing card content.
guru_list_knowledge_agents
Get available knowledge agents and their IDs. Always call this first before using guru_search_documents or guru_answer_generation tools, as both require an agentId parameter. Each agent has different expertise areas and data sources configured.
guru_get_card_by_id
Get full card content in original HTML format by card ID
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 Guru call is logged with the person and the client that made it.
Access by role
Gateway
People reach only the Guru tools their team or role allows.
Request and response blocking
Gateway
A risk policy scoped to Guru 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
How are OpenCode's Guru sessions measured?
Where is Guru tool output blocked for OpenCode?
How do OpenCode users get Guru?
Are Guru calls from OpenCode logged?
Connect more