MCP Gateway · Cursor
Connect Grain to Cursor
Your private notes from a planning call are usually more useful than the official summary. With Grain connected to Cursor through the Speakeasy MCP Gateway, the agent can read those notes and search past meetings from the editor. Cursor hooks send each tool call to Speakeasy and fail closed, so nothing runs without an allow.
- Category
- Productivity
- Tools
- 22
- Authentication
- OAuth
- Cursor
- Editor and terminal
Behind the MCP Gateway
Run Grain MCP behind the MCP Gateway
One URL for every agent, sign-in through your IdP, RBAC down to the tool, and every Grain call inspected and logged.
Set up
Add Grain to Cursor in 4 steps
- 01
Add Grain from the catalog
An admin finds Grain 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.
Grain uses OAuth. Servers that support dynamic client registration get their OAuth configuration applied automatically.
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 Grain
Give teams the
mcp:connectscope on the Grain server through team access or a role. The organization gateway works out each person's servers from their live access, so granting access adds Grain 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 Grain from Cursor
The first time Cursor connects, it opens a browser so the person can sign in to Speakeasy through your identity provider.
Grain needs its own OAuth grant, so each person connects it once. Until they do, Grain calls fail while the rest of the gateway keeps working.
From then on, Grain'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 Grain
Keep your own call notes in view
Ask Cursor for the private notes you took during a planning meeting and keep them in the chat while you work through the tasks they describe.
Search calls for an error message
Paste an error string or feature name and Cursor searches meeting segments for it, showing which calls discussed it and what the speakers said.
Tag meetings that shaped a feature
Once a feature ships, Cursor tags the meetings that led to it, creating the tag if it's new, so the next person can find the history in Grain.
Tools
22 tools
Each Grain tool can be allowed or denied per team and role at the MCP Gateway before Cursor sees it.
myself
Get information about the logged-in Grain user.
list_meetings
Returns a filtered list of Grain meetings you have access to, ordered by most recent.
list_attended_meetings
Returns a filtered list of Grain meetings you have attended, ordered by most recent.
fetch_meeting
Fetches information about a single Grain meeting by ID. The response format is the same as is returned by list_meetings.
fetch_meeting_notes
Fetches the AI notes payload from a single Grain meeting by ID. In some cases, older meetings may not have had notes generated for them. In these cases you can use fetch_meeting_transcript instead to determine the content of the meeting.
fetch_meeting_action_items
Fetches the action items extracted from a single Grain meeting by ID. Action items include the task description, timestamp, status (pending or completed), due date, and the person assigned to the action item (if any).
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 Grain call is logged with the person and the client that made it.
Access by role
Gateway
People reach only the Grain tools their team or role allows.
Request and response blocking
Gateway
A risk policy scoped to Grain 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
Is every Grain call from Cursor tied to a person?
Do Grain tools work in Cursor Cloud agents?
How do Cursor users get Grain?
Are Grain calls from Cursor logged?
Connect more