MCP Gateway · Cursor
Connect Glyphic to Cursor
Product engineers in Cursor can check how customers talk about a feature without asking sales for notes. Glyphic brings sales call transcripts and conversation analytics into the editor's chat through the Speakeasy gateway. Speakeasy reviews each prompt and Glyphic call before Cursor runs it, nothing proceeds if that review can't happen, and the developer's email travels with each event.
- Category
- Sales & CRM
- Authentication
- API key
- Cursor
- Editor and terminal
Behind the MCP Gateway
Run Glyphic MCP behind the MCP Gateway
One URL for every agent, sign-in through your IdP, RBAC down to the tool, and every Glyphic call inspected and logged.
Set up
Add Glyphic to Cursor in 4 steps
- 01
Add Glyphic from the catalog
An admin finds Glyphic 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.
Glyphic 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 Glyphic
Give teams the
mcp:connectscope on the Glyphic server through team access or a role. The organization gateway works out each person's servers from their live access, so granting access adds Glyphic 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 Glyphic 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, Glyphic'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 Glyphic
Match UI copy to customer language
Ask Cursor how prospects describe a feature on sales calls, then rename labels and help text in the component you're editing to match the words they use.
Check feedback on a shipped change
After a release, Cursor searches recent sales calls for mentions of the feature you shipped and summarizes what buyers liked and what confused them.
Prepare for a technical sales call
Engineers joining a sales call ask Cursor for the deal insights and earlier call transcripts, so they know the prospect's stack and open questions beforehand.
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 Glyphic call is logged with the person and the client that made it.
Access by role
Gateway
People reach only the Glyphic tools their team or role allows.
Request and response blocking
Gateway
A risk policy scoped to Glyphic 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 Glyphic usage in Cursor be capped?
Does anyone paste a Glyphic API key into Cursor?
How do Cursor users get Glyphic?
Are Glyphic calls from Cursor logged?
Connect more