Skip to main content
Back to the Pylon MCP server

MCP Gateway · OpenCode

Pylon icon

Connect Pylon to OpenCode

On-call developers using OpenCode can check Pylon during an incident to see which customers are writing in and what they report. The OpenCode plugin sends each prompt and tool call to Speakeasy, which allows or denies it before it runs, and tool output is blocked at the gateway when policy requires it.

Category
Productivity
Authentication
OAuth
OpenCode
Terminal

Behind the MCP Gateway

Run Pylon MCP behind the MCP Gateway

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

Deploy on MCP Gateway

Set up

Add Pylon to OpenCode in 4 steps

  1. 01

    Add Pylon from the catalog

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

    Pylon 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.

  2. 02

    Choose who can use Pylon

    Give teams the mcp:connect scope on the Pylon server through team access or a role. OpenCode connects to the Pylon 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 Pylon from OpenCode

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

    Pylon needs its own OAuth grant, so each person connects it once. Until they do, Pylon calls fail while the rest of the gateway keeps working.

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

Watch support volume during an incident

While you work on an outage from the terminal, ask OpenCode how many new Pylon issues have come in and which accounts opened them.

Post an incident note to issues

Once the cause is known, OpenCode updates the related Pylon issues with a short technical note so support can respond with the same explanation.

Pull logs mentioned in a conversation

Read a Pylon conversation for the timestamps, request IDs and error text a customer shared, then search your own logs for those exact values.

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

Access by role

Gateway

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

Request and response blocking

Gateway

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

Can the device agent manage Pylon access in OpenCode?
The device agent installs and maintains OpenCode's observability package. The Pylon server itself is added to the mcp block of your OpenCode config, because OpenCode doesn't receive MCP servers from plugins.
Is Pylon customer data inspected on the way through?
Yes. Prompt injection detection and PII redaction run on every Pylon tool call at the gateway, and each call is logged against a named employee.
How do OpenCode users get Pylon?
An admin adds Pylon 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 Pylon tools their access allows.
Are Pylon calls from OpenCode logged?
Yes. Pylon 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

Pylon in other clients

AI everywhere.

Control here.