MCP Gateway · OpenCode
Connect Ordinal to OpenCode
Social schedules sometimes need bulk changes at short notice, such as pausing everything during an outage or moving a week of posts. OpenCode can make those changes from a terminal session against Ordinal, added as a remote server in its mcp config. Speakeasy's gateway limits which Ordinal tools each role can call, and the OpenCode plugin allows or denies each prompt and tool call before it runs.
- Category
- Productivity
- Tools
- 63
- Authentication
- API key
- OpenCode
- Terminal
Behind the MCP Gateway
Run Ordinal MCP behind the MCP Gateway
One URL for every agent, sign-in through your IdP, RBAC down to the tool, and every Ordinal call inspected and logged.
Set up
Add Ordinal to OpenCode in 4 steps
- 01
Add Ordinal from the catalog
An admin finds Ordinal 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.
Ordinal 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.
- 02
Choose who can use Ordinal
Give teams the
mcp:connectscope on the Ordinal server through team access or a role. OpenCode connects to the Ordinal 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 Ordinal 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, Ordinal'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 Ordinal
Pause scheduled posts during an incident
OpenCode lists the workspace's posts, finds the ones scheduled in the next few days, and unschedules them. Each one moves to Finalized and its pending publishes are cancelled.
Move a week of posts in one pass
Give OpenCode a new start date and it reschedules each affected post, after checking which scheduling profiles are connected to the workspace.
Add a teammate to the workspace
OpenCode checks the current users and pending invites, then invites a new teammate by email. Anyone with an Ordinal account joins immediately; others receive an email.
Tools
63 tools
Each Ordinal tool can be allowed or denied per team and role at the MCP Gateway before OpenCode sees it.
analytics-linkedin-followers
LinkedIn follower growth
analytics-linkedin-posts
LinkedIn post analytics
analytics-x-followers
X follower growth
analytics-x-posts
X post analytics
analytics-cpm-get
Get CPM Values
analytics-cpm-update
Update CPM 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 Ordinal call is logged with the person and the client that made it.
Access by role
Gateway
People reach only the Ordinal tools their team or role allows.
Request and response blocking
Gateway
A risk policy scoped to Ordinal 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 an unscheduled Ordinal post be scheduled again?
How does OpenCode report usage for Ordinal sessions?
How do OpenCode users get Ordinal?
Are Ordinal calls from OpenCode logged?
Connect more