Skip to main content
Back to the Pylon MCP server

MCP Gateway · Claude Cowork

Pylon icon

Connect Pylon to Claude Cowork

A quarterly business review needs every support issue, conversation and contact for an account in one place. Cowork can collect that from Pylon over a longer task and turn it into a finished document. Agent hooks send each prompt to Speakeasy before the step runs, and OTLP export from the Cowork tab ties the session to a person.

Category
Productivity
Authentication
OAuth
Claude Cowork
Cowork tab in Claude Desktop

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 Cowork 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. Claude Cowork connects to the Pylon server's own URL, and the server's authorization decides who can connect and which tools they can call.

  3. 03

    Connect Claude Cowork

    Sync the organization's plugin marketplace into Claude, then make the plugins available in Cowork.

    New MCP servers join the project's default plugin automatically. Each server's overview page shows which plugin it is published to, with Publish or Update to change it.

    Add the importing admin's GitHub username as a marketplace collaborator and accept the invite. Only that admin needs it.

    In Claude Organization settings > Plugins & skills, select Add > Sync from GitHub and pick the organization's plugin repository. The Claude GitHub App must be installed on it.

    Mark the observability plugin Required, and set the plugin that carries this server to Available to install or Installed by default.

    In the Cowork tab's Monitoring settings, set the OTLP endpoint, protocol and headers.

  4. 04

    Sign in and use Pylon from Claude Cowork

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

Cowork reads the synced repository, so a new session picks up plugin changes. Members who receive plugins through Cowork don't need a GitHub invitation.

Use cases

What Claude Cowork users do with Pylon

Draft a quarterly business review

Cowork gathers the quarter's support issues and conversations for an account, summarizes response trends and open problems, and writes the support section of the review deck.

Clean up stale support issues

Work through the open Pylon issues that have had no reply in weeks, read each conversation, and update the ones that are already resolved.

Hand over a book of accounts

When an account manager changes, Cowork reads each account's contacts and recent conversations in Pylon and writes a handover note for the new owner.

Control

What Speakeasy can see and stop in Claude Cowork

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

Prompt blocking

Claude Cowork

Agent hooks send each prompt to Speakeasy, which allows or denies it before the step runs.

Session telemetry

Claude Cowork

Cowork's OTLP export ties sessions to people and feeds observability.

Anthropic inference hooks

Claude Cowork

On Claude Enterprise, prompts can be checked before inference (beta).

  • Neither the device agent nor MDM reaches Cowork, so the Claude-side setup always applies.
  • Personal Claude accounts can't be governed in Cowork.

Questions

Frequently asked questions

Can personal Claude accounts use Pylon in Cowork?
Personal Claude accounts can't be governed in Cowork. The Pylon plugin reaches members through the organization's synced marketplace.
How do Cowork members get the Pylon plugin?
An admin syncs the organization's plugin repository under Organization settings > Plugins & skills and sets the plugin to Available to install or Installed by default. Members who receive plugins through Cowork don't need a GitHub invitation.
How do Claude Cowork users get Pylon?
An admin adds Pylon from the Speakeasy MCP Catalog and grants access by team or role. Sync the organization's plugin marketplace into Claude, then make the plugins available in Cowork. Each person then sees only the Pylon tools their access allows.
Are Pylon calls from Claude Cowork 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.