Skip to main content
Back to the Pylon MCP server

MCP Gateway · Claude

Pylon icon

Connect Pylon to Claude

Account managers and support leads spend much of the day reading Pylon. In Claude they can ask about an account's open issues, catch up on long conversations and update records, through the Speakeasy MCP Gateway. No client ID or secret is needed, and each person only sees the servers their role can reach.

Category
Productivity
Authentication
OAuth
Claude
Web, desktop and mobile

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 Claude 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 Claude

    Add the gateway URL as a custom connector, then connect it from Customize > Connectors.

    On Team and Enterprise plans, an Owner opens Organization settings > Connectors, chooses Add > Custom > Web and pastes the gateway URL.

    Each person opens Customize > Connectors and clicks Connect to sign in.

    On Pro and Max plans, each person adds it themselves under Customize > Connectors, with + Add > Add custom connector.

  4. 04

    Sign in and use Pylon from Claude

    The first time Claude 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, limited to what the person's access allows, and every call lands in the gateway's tool logs.

No client ID or secret is needed: the gateway's sign-in handles client registration. Each person only sees the servers their role can reach.

Use cases

What Claude users do with Pylon

Prepare for a customer check-in

Before a call, ask Claude for the account's open support issues and recent conversations, and get a short brief on what the customer is waiting for.

Catch up on a long thread

When an escalated conversation has dozens of replies, have Claude read it and summarize the problem, what has been tried and what the customer asked for last.

Keep contact records current

After a meeting, ask Claude to update the account's contacts in Pylon with new names, roles and the person who now owns the relationship.

Control

What Speakeasy can see and stop in Claude

The gateway covers every client the same way. The rest depends on what Claude 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. MCP-scoped policies are enabled per organization.

Anthropic inference hooks

Claude

On Claude Enterprise, each prompt is sent to Speakeasy before inference and denied prompts are blocked (beta). Inference hooks can't rewrite or redact a prompt.

Conversation import

Claude

Claude conversations can be imported through Anthropic's Compliance API for review after the fact.

  • Custom connectors need a Claude plan that supports them.
  • Budgets don't cover Claude web and desktop usage.

Questions

Frequently asked questions

Can support staff use Pylon in Claude on a Pro plan?
On Pro and Max plans, each person adds the gateway themselves under Customize > Connectors > Add custom connector. Custom connectors need a Claude plan that supports them.
Does Pylon access in Claude end when someone leaves?
Yes. Sessions authenticate through your identity provider, so access ends when the employee leaves the directory. Agents never hold a Pylon credential.
How do Claude users get Pylon?
An admin adds Pylon from the Speakeasy MCP Catalog and grants access by team or role. Add the gateway URL as a custom connector, then connect it from Customize > Connectors. Each person then sees only the Pylon tools their access allows.
Are Pylon calls from Claude 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.