MCP Gateway · Claude Code
Connect Ordinal to Claude Code
Release notes and launch screenshots already sit in the repository, so the first draft of a social announcement can start there too. Claude Code can turn a tag or changelog into Ordinal content without a context switch. Speakeasy's gateway authenticates each session with your IdP, limits developers to the Ordinal tools their team is granted, and records every call in an audit log tied to a named employee.
- Category
- Productivity
- Tools
- 63
- Authentication
- API key
- Claude Code
- CLI
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 Claude Code 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. The organization gateway works out each person's servers from their live access, so granting access adds Ordinal to their gateway on the next call, and removing it takes it away. - 03
Connect Claude Code
Add the organization gateway as an HTTP MCP server, then authenticate from /mcp.
Run the command below with your organization gateway URL.
Open
/mcpin Claude Code and choose Authenticate to sign in.claude mcp add --transport http --scope user \ 'speakeasy' \ 'https://<organization host>/mcp/gateway/<organization slug>' - 04
Sign in and use Ordinal from Claude Code
The first time Claude Code 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 Claude Code, limited to what the person's access allows, and every call lands in the gateway's tool logs.
To roll it out to a whole team, publish the server in a plugin and register the plugin marketplace in Claude Code's managed settings, so every member gets it without running the command. The device agent can also write and reapply these settings on each laptop.
Use cases
What Claude Code users do with Ordinal
Draft a launch post from the changelog
Ask Claude Code to read the latest changelog entry and save it as an Ordinal idea for LinkedIn or X, so marketing can shape it before it reaches the calendar.
Attach release screenshots to a post
Claude Code uploads screenshots from a URL, polls until each upload is ready, then uses the returned asset IDs when it creates the announcement post.
Send Ordinal events to your service
When an internal tool should react to Ordinal activity, Claude Code lists the workspace's webhooks and creates one for the topics your service handles.
Tools
63 tools
Each Ordinal tool can be allowed or denied per team and role at the MCP Gateway before Claude Code 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 Claude Code
The gateway covers every client the same way. The rest depends on what Claude Code 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 Claude Code. MCP-scoped policies are enabled per organization.
Prompt and tool-call blocking
Claude Code
Agent hooks send each prompt and tool call to Speakeasy, which allows or denies it before Claude Code runs it.
User attribution
Claude Code
Claude Code's OpenTelemetry exporter ties each session to a named person. Without it, activity can't be attributed.
Budgets
Claude Code
Spend limits can block Claude Code traffic once a budget is reached.
Device agent and MDM
Claude Code
The device agent installs the marketplace, plugin and telemetry settings and reapplies them every minute. It deploys through MDM.
Anthropic inference hooks
Claude Code
On Claude Enterprise, prompts can be checked before inference with nothing installed on the device (beta).
- Claude Code on the web doesn't use the laptop setup. It needs the device agent in a shared Anthropic-hosted environment.
- Plugin marketplace URLs for Claude Code carry an access token, so share install snippets only through a private channel.
Questions
Frequently asked questions
Can Claude Code draft Ordinal posts without being able to schedule them?
Does each developer need an Ordinal API key in Claude Code?
How do Claude Code users get Ordinal?
Are Ordinal calls from Claude Code logged?
Connect more