Skip to main content
Back to the Pylon MCP server

MCP Gateway · Cursor

Pylon icon

Connect Pylon to Cursor

Support context helps when you are deciding how a fix should behave. In Cursor, the agent can query Pylon for the issues and conversations tied to the component you have open, then note the outcome on the issue. Every Cursor hook event carries the developer's email, so each Pylon call is attributed.

Category
Productivity
Authentication
OAuth
Cursor
Editor and terminal

Behind the MCP Gateway

Run Pylon MCP behind the MCP Gateway

One URL for every agent, sign-in through your IdP, RBAC down to the tool, and every Pylon call inspected and logged.

Deploy on MCP Gateway

Set up

Add Pylon to Cursor in 4 steps

  1. 01

    Add Pylon from the catalog

    An admin finds Pylon 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.

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

  2. 02

    Choose who can use Pylon

    Give teams the mcp:connect scope on the Pylon server through team access or a role. The organization gateway works out each person's servers from their live access, so granting access adds Pylon to their gateway on the next call, and removing it takes it away.

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

  4. 04

    Sign in and use Pylon from Cursor

    The first time Cursor connects, it opens a browser so the person can sign in to Speakeasy through your identity provider.

    Pylon needs its own OAuth grant, so each person connects it once. Until they do, Pylon calls fail while the rest of the gateway keeps working.

    From then on, Pylon'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 Pylon

See complaints about this component

While editing a feature, ask Cursor to search Pylon for recent support issues that mention it, and read the customer conversations before you change its behavior.

Answer a support question about code

When support asks how a setting works, Cursor reads the Pylon issue, finds the answer in the source, and adds a clear explanation the support agent can pass on.

Check the account behind a bug

Look up the account and contacts linked to a support issue, so you know the customer's setup before you try to reproduce the problem locally.

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 Pylon call is logged with the person and the client that made it.

Access by role

Gateway

People reach only the Pylon tools their team or role allows.

Request and response blocking

Gateway

A risk policy scoped to Pylon 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 Speakeasy stop a Pylon call from Cursor?
Yes. Cursor hooks send each prompt and tool call to Speakeasy, which allows or denies it before Cursor runs it, and they fail closed.
How does a Cursor team get Pylon without GitHub access?
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.
How do Cursor users get Pylon?
An admin adds Pylon from the Speakeasy MCP Catalog and grants access by team or role. Add the gateway to Cursor in one click from the Organization Gateway page. Each person then sees only the Pylon tools their access allows.
Are Pylon calls from Cursor logged?
Yes. Pylon 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

Pylon in other clients

AI everywhere.

Control here.