Skip to main content
Back to the Glyphic MCP server

MCP Gateway · OpenCode

Glyphic icon

Connect Glyphic to OpenCode

OpenCode can read sales call data from the terminal once Glyphic is added to its mcp config as a remote server. Solutions and support engineers use it to see what a customer said about their setup while working on their issue. The OpenCode plugin asks Speakeasy to approve every prompt and tool call, and reports token and cost totals per turn.

Category
Sales & CRM
Authentication
API key
OpenCode
Terminal

Behind the MCP Gateway

Run Glyphic MCP behind the MCP Gateway

One URL for every agent, sign-in through your IdP, RBAC down to the tool, and every Glyphic call inspected and logged.

Deploy on MCP Gateway

Set up

Add Glyphic to OpenCode in 4 steps

  1. 01

    Add Glyphic from the catalog

    An admin finds Glyphic 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.

    Glyphic authenticates with an API key. Enter it under Upstream headers in the install dialog, or later on the server's Settings tab. The key is stored on the server, sent with every upstream request, and never reaches anyone's client configuration.

    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.

  2. 02

    Choose who can use Glyphic

    Give teams the mcp:connect scope on the Glyphic server through team access or a role. OpenCode connects to the Glyphic server's own URL, and the server's authorization decides who can connect and which tools they can call.

  3. 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 mcp block of your OpenCode config with type set to remote.

    Restart OpenCode and sign in when prompted.

    {
      "mcp": {
        "<server slug>": {
          "type": "remote",
          "url": "<URL from the hosted install page>"
        }
      }
    }
  4. 04

    Sign in and use Glyphic from OpenCode

    The first time OpenCode connects, it opens a browser so the person can sign in to Speakeasy through your identity provider.

    From then on, Glyphic'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 Glyphic

Learn a customer's setup before debugging

Before digging into a customer's issue, ask OpenCode for their sales call transcripts and pull out what they said about their environment and integrations.

Build a demo from the prospect's case

Solutions engineers have OpenCode read a prospect's discovery call, then script demo data and a sample project that mirror the use case they described.

Pull call analytics into a script

Ask OpenCode for Glyphic's conversation analytics on a set of deals and write them to a CSV for a product analysis notebook.

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 Glyphic call is logged with the person and the client that made it.

Access by role

Gateway

People reach only the Glyphic tools their team or role allows.

Request and response blocking

Gateway

A risk policy scoped to Glyphic 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

Where is Glyphic output blocked for OpenCode?
Tool output is blocked at the gateway rather than in OpenCode's hooks. Prompt injection detection and PII redaction run on every Glyphic tool call there.
Who keeps the OpenCode observability package up to date?
The device agent installs and maintains the observability package. It can also be installed from a ZIP or with speakeasy-hooks install --provider=opencode.
How do OpenCode users get Glyphic?
An admin adds Glyphic from the Speakeasy MCP Catalog and grants access by team or role. Add the server to OpenCode's own mcp config block as a remote server. Each person then sees only the Glyphic tools their access allows.
Are Glyphic calls from OpenCode logged?
Yes. Glyphic calls go through the MCP Gateway, which logs each tool call and attributes it to the person and the client that made it.

Connect more

Glyphic in other clients

AI everywhere.

Control here.