Skip to main content
Back to the Zapier MCP server

MCP Gateway · OpenCode

Zapier icon

Connect Zapier to OpenCode

OpenCode users who run small automations from the terminal can route them through Zapier actions instead of writing a client for each app. The server sits in OpenCode's mcp config as a remote entry, and its one tool returns the page where those actions are managed. Speakeasy's gateway controls which roles can reach Zapier, and the OpenCode plugin allows or denies each tool call before it runs.

Category
Productivity
Tools
1
OpenCode
Terminal

Behind the MCP Gateway

Run Zapier MCP behind the MCP Gateway

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

Deploy on MCP Gateway

Before you start

What Zapier needs first

No admin needed; the Zapier account manager only if MCP is disabled does the Zapier side of the setup.

  • Zapier MCP is available on every Zapier plan.
  • If Zapier MCP is disabled, the Zapier account manager must enable it for the workspace.
  • You do not need an app connection to establish the MCP connection.
Full Zapier setup guide in the docs

Set up

Add Zapier to OpenCode in 4 steps

  1. 01

    Add Zapier from the catalog

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

    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 Zapier

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

Set up actions for a terminal routine

Before scripting a routine that touches other apps, ask OpenCode for the Zapier configuration URL and add the actions that routine will call.

get_configuration_url

Edit an action without leaving the shell

OpenCode prints the configuration link in the session, so changing an action's setup is one click away from the command that needs it.

get_configuration_url

Clear out actions nobody uses

Every so often, have OpenCode return the configuration page and remove the Zapier actions that no current script or terminal routine relies on anymore.

get_configuration_url

Tools

1 tool

Each Zapier tool can be allowed or denied per team and role at the MCP Gateway before OpenCode sees it.

get_configuration_url

Returns the URL where users can configure this MCP server - adding, editing, or removing actions. Provide this URL to users who want to customize their available tools.

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

Access by role

Gateway

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

Request and response blocking

Gateway

A risk policy scoped to Zapier 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 get the Zapier server from a plugin?
No. OpenCode doesn't receive MCP servers from plugins, so each person adds the server's URL from its hosted install page to their OpenCode config.
Where is Zapier tool output blocked for OpenCode users?
At the gateway rather than in OpenCode's hooks. Prompt injection detection and PII redaction run on every Zapier tool call there.
How do OpenCode users get Zapier?
An admin adds Zapier 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 Zapier tools their access allows.
Are Zapier calls from OpenCode logged?
Yes. Zapier 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

Zapier in other clients

AI everywhere.

Control here.