Skip to main content
Back to the Ordinal MCP server

MCP Gateway · Claude

Ordinal icon

Connect Ordinal to Claude

Social and brand managers spend much of their week moving between ideas, reviews and follower numbers in Ordinal. In Claude, they can ask for each of those in plain language. After an Owner adds the Speakeasy gateway as a custom connector, everyone connects from Customize > Connectors and sees only the Ordinal tools their role can reach, with no client ID or secret to manage.

Category
Productivity
Tools
63
Authentication
API key
Claude
Web, desktop and mobile

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.

Deploy on MCP Gateway

Set up

Add Ordinal to Claude in 4 steps

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

  2. 02

    Choose who can use Ordinal

    Give teams the mcp:connect scope 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.

  3. 03

    Connect Claude

    Add the gateway URL as a custom connector, then connect it from Customize > Connectors.

    On Team and Enterprise plans, an Owner opens Organization settings > Connectors, chooses Add > Custom > Web and pastes the gateway URL.

    Each person opens Customize > Connectors and clicks Connect to sign in.

    On Pro and Max plans, each person adds it themselves under Customize > Connectors, with + Add > Add custom connector.

  4. 04

    Sign in and use Ordinal from Claude

    The first time Claude 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, limited to what the person's access allows, and every call lands in the gateway's tool logs.

No client ID or secret is needed: the gateway's sign-in handles client registration. Each person only sees the servers their role can reach.

Use cases

What Claude users do with Ordinal

Brainstorm ideas into the backlog

Talk through a campaign with Claude, check the existing ideas so nothing is duplicated, and save the best new ones to Ordinal for LinkedIn or X.

ideas-listideas-create

See where a post is in review

Ask Claude for a post's approval requests and its comment thread, and get a short summary of who has signed off and what feedback is still open.

approvals-listcomments-list

Track LinkedIn follower growth

Ask Claude how a company or executive LinkedIn profile has grown over the quarter, and get the follower history as a short written summary for a team update.

analytics-linkedin-followers

Tools

63 tools

Each Ordinal tool can be allowed or denied per team and role at the MCP Gateway before Claude 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

See all 63 tools

Control

What Speakeasy can see and stop in Claude

The gateway covers every client the same way. The rest depends on what Claude 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. MCP-scoped policies are enabled per organization.

Anthropic inference hooks

Claude

On Claude Enterprise, each prompt is sent to Speakeasy before inference and denied prompts are blocked (beta). Inference hooks can't rewrite or redact a prompt.

Conversation import

Claude

Claude conversations can be imported through Anthropic's Compliance API for review after the fact.

  • Custom connectors need a Claude plan that supports them.
  • Budgets don't cover Claude web and desktop usage.

Questions

Frequently asked questions

Can Claude Enterprise block prompts sent to Ordinal tools?
On Claude Enterprise, each prompt is sent to Speakeasy before inference and denied prompts are blocked (beta). Inference hooks can't rewrite or redact a prompt.
Can Claude conversations about Ordinal be reviewed later?
Yes. Claude conversations can be imported through Anthropic's Compliance API for review after the fact, and every Ordinal tool call is logged at the gateway against a named employee.
How do Claude users get Ordinal?
An admin adds Ordinal from the Speakeasy MCP Catalog and grants access by team or role. Add the gateway URL as a custom connector, then connect it from Customize > Connectors. Each person then sees only the Ordinal tools their access allows.
Are Ordinal calls from Claude logged?
Yes. Ordinal 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

Ordinal in other clients

AI everywhere.

Control here.