MCP Gateway · Claude Cowork
Connect Ordinal to Claude Cowork
Planning a month of social content takes many steps: turning ideas into dated posts, routing them for sign-off and reporting on results. Cowork can run each of those as a longer task in Ordinal for a marketing team. The server comes through the organization's synced plugin, Cowork's OTLP export ties sessions to people, and Speakeasy's agent hooks decide on each prompt before the step runs.
- Category
- Productivity
- Tools
- 63
- Authentication
- API key
- Claude Cowork
- Cowork tab in Claude Desktop
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 Cowork 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. Claude Cowork 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 Claude Cowork
Sync the organization's plugin marketplace into Claude, then make the plugins available in Cowork.
New MCP servers join the project's default plugin automatically. Each server's overview page shows which plugin it is published to, with Publish or Update to change it.
Add the importing admin's GitHub username as a marketplace collaborator and accept the invite. Only that admin needs it.
In Claude Organization settings > Plugins & skills, select Add > Sync from GitHub and pick the organization's plugin repository. The Claude GitHub App must be installed on it.
Mark the observability plugin Required, and set the plugin that carries this server to Available to install or Installed by default.
In the Cowork tab's Monitoring settings, set the OTLP endpoint, protocol and headers.
- 04
Sign in and use Ordinal from Claude Cowork
The first time Claude Cowork 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 Cowork, limited to what the person's access allows, and every call lands in the gateway's tool logs.
Cowork reads the synced repository, so a new session picks up plugin changes. Members who receive plugins through Cowork don't need a GitHub invitation.
Use cases
What Claude Cowork users do with Ordinal
Turn the idea backlog into a calendar
Cowork reviews the open ideas, assigns publish dates to the ones that fit the month's themes, and schedules the resulting posts on connected profiles.
Route a batch of posts for approval
For each draft, Cowork creates approval requests, subscribes the reviewers so they follow the post, and leaves a comment explaining what needs a decision.
Build a quarterly results report
Cowork collects LinkedIn and X post analytics for the quarter, applies the workspace's CPM values to estimate earned media value, and writes the report.
Tools
63 tools
Each Ordinal tool can be allowed or denied per team and role at the MCP Gateway before Claude Cowork 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 Cowork
The gateway covers every client the same way. The rest depends on what Claude Cowork 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 Cowork. MCP-scoped policies are enabled per organization.
Prompt blocking
Claude Cowork
Agent hooks send each prompt to Speakeasy, which allows or denies it before the step runs.
Session telemetry
Claude Cowork
Cowork's OTLP export ties sessions to people and feeds observability.
Anthropic inference hooks
Claude Cowork
On Claude Enterprise, prompts can be checked before inference (beta).
- Neither the device agent nor MDM reaches Cowork, so the Claude-side setup always applies.
- Personal Claude accounts can't be governed in Cowork.
Questions
Frequently asked questions
What happens to Ordinal ideas that Cowork archives?
Can personal Claude accounts use Ordinal in Cowork?
How do Claude Cowork users get Ordinal?
Are Ordinal calls from Claude Cowork logged?
Connect more