MCP Gateway · Cursor
Connect Ordinal to Cursor
Developer relations teams write about the code they ship, and the post often starts in the same editor as the pull request. Cursor can save that draft as an Ordinal idea, tag the right people and set up a Slack announcement for when it goes out. Speakeasy's gateway logs each Ordinal call with the developer's email, and Cursor hooks check every prompt and tool call first.
- Category
- Productivity
- Tools
- 63
- Authentication
- API key
- Cursor
- Editor and 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 Cursor 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 Cursor
Add the gateway to Cursor in one click from the Organization Gateway page.
On the Organization Gateway page in Speakeasy, choose Cursor under Install.
Click Add to Cursor to add the gateway to Cursor's MCP settings, then sign in when Cursor prompts you.
- 04
Sign in and use Ordinal from Cursor
The first time Cursor 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 Cursor, limited to what the person's access allows, and every call lands in the gateway's tool logs.
For a whole team, a Cursor team admin imports the plugin marketplace under Settings > Plugins > Import and turns on Serve Marketplace From Cursor, so members install without GitHub access.
Use cases
What Cursor users do with Ordinal
Save a post idea from a pull request
While a feature branch is open, ask Cursor to write a short LinkedIn or X idea from the change description and save it in Ordinal for the content team to pick up.
Mention contributors on LinkedIn
Give Cursor the LinkedIn usernames of the people who worked on a release, and it looks up the mention format for each so the post tags them correctly.
Announce a post in Slack when it publishes
Cursor lists the connected Slack marketing channels and creates a Slack boost on the post, so Ordinal notifies that channel when the post goes live.
Tools
63 tools
Each Ordinal tool can be allowed or denied per team and role at the MCP Gateway before Cursor 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 Cursor
The gateway covers every client the same way. The rest depends on what Cursor 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 Cursor. MCP-scoped policies are enabled per organization.
Prompt and tool-call blocking
Cursor
Cursor hooks send each prompt and tool call to Speakeasy, which allows or denies it before Cursor runs it, and fail closed.
User attribution
Cursor
Every Cursor hook event carries the user's email.
Budgets
Cursor
Spend limits can block Cursor traffic once a budget is reached. Connect the Cursor Admin API for dollar spend.
Device agent and MDM
Cursor
The device agent installs the marketplace and plugins and reapplies them every minute.
- Cursor Cloud agents need a checked-in
.cursor/hooks.json. Session and MCP-specific hooks don't run there. - After a plugin update, members run Developer: Reload Window.
Questions
Frequently asked questions
Can a post have more than one Slack boost?
How does an Ordinal plugin change reach Cursor?
How do Cursor users get Ordinal?
Are Ordinal calls from Cursor logged?
Connect more