MCP Gateway · Claude Code
Connect Pylon to Claude Code
Bugs that customers report usually reach engineering through Pylon first. With Pylon behind the Speakeasy MCP Gateway, Claude Code can read the support issue and the conversation around it while you fix the code, then update the issue when you're done. Hooks check each prompt and tool call before Claude Code runs it.
- Category
- Productivity
- Authentication
- OAuth
- Claude Code
- CLI
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.
Set up
Add Pylon to Claude Code in 4 steps
- 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.
- 02
Choose who can use Pylon
Give teams the
mcp:connectscope 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. - 03
Connect Claude Code
Add the organization gateway as an HTTP MCP server, then authenticate from /mcp.
Run the command below with your organization gateway URL.
Open
/mcpin Claude Code and choose Authenticate to sign in.claude mcp add --transport http --scope user \ 'speakeasy' \ 'https://<organization host>/mcp/gateway/<organization slug>' - 04
Sign in and use Pylon from Claude Code
The first time Claude Code 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 Claude Code, limited to what the person's access allows, and every call lands in the gateway's tool logs.
To roll it out to a whole team, publish the server in a plugin and register the plugin marketplace in Claude Code's managed settings, so every member gets it without running the command. The device agent can also write and reapply these settings on each laptop.
Use cases
What Claude Code users do with Pylon
Read the customer report before fixing
Ask Claude Code to pull the Pylon support issue and its conversation, so the reproduction steps and the customer's own words sit next to the code you're about to change.
Tell support the fix has shipped
When your change is merged, have Claude Code update the related Pylon issue with what was fixed, so the support team can reply to the customer without chasing you.
Check how many accounts are affected
Before deciding on a hotfix, query Pylon for other support issues and accounts that mention the same error, and judge how far it has spread.
Control
What Speakeasy can see and stop in Claude Code
The gateway covers every client the same way. The rest depends on what Claude Code 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 Claude Code. MCP-scoped policies are enabled per organization.
Prompt and tool-call blocking
Claude Code
Agent hooks send each prompt and tool call to Speakeasy, which allows or denies it before Claude Code runs it.
User attribution
Claude Code
Claude Code's OpenTelemetry exporter ties each session to a named person. Without it, activity can't be attributed.
Budgets
Claude Code
Spend limits can block Claude Code traffic once a budget is reached.
Device agent and MDM
Claude Code
The device agent installs the marketplace, plugin and telemetry settings and reapplies them every minute. It deploys through MDM.
Anthropic inference hooks
Claude Code
On Claude Enterprise, prompts can be checked before inference with nothing installed on the device (beta).
- Claude Code on the web doesn't use the laptop setup. It needs the device agent in a shared Anthropic-hosted environment.
- Plugin marketplace URLs for Claude Code carry an access token, so share install snippets only through a private channel.
Questions
Frequently asked questions
Can I limit what Claude Code does in Pylon?
Does customer data from Pylon get redacted?
How do Claude Code users get Pylon?
Are Pylon calls from Claude Code logged?
Connect more