Pylon MCP server

A Pylon MCP server exposes Pylon to AI agents as Model Context Protocol tools. Instead of a custom integration per agent, any MCP client can connect to the server and call its tools to work with Pylon. The server in this catalog is the official Pylon MCP server, which authenticates with OAuth.

Agents can query and manage B2B support issues, conversations, accounts, and contacts. The registry has not published an individual tool list for this server yet, so no tools are shown on this page.

Connecting the Pylon MCP server directly to each client means a separate credential per developer, no inventory of who can reach Pylon through an agent, and no record of what agents did with it. An MCP gateway sits between every agent and the Pylon server, so sign-in runs through your identity provider, role-based access decides which teams can call which Pylon tools, and every call is inspected and logged in one place. The Speakeasy MCP Gateway applies those controls to Pylon and to every other server in your catalog.

Add the Pylon server from the Speakeasy MCP catalog and every agent reaches it through one gateway URL, next to the rest of your approved servers. Authentication uses OAuth 2.1 with PKCE and dynamic client registration, sign-in runs through your identity provider, and role-based access controls decide which teams can use which Pylon tools. Every prompt, response, and tool call is inspected and logged at the gateway.

Community-built Pylon MCP servers wrap the same Pylon surface but are not vendor-maintained, and most authenticate with a static credential that gives an agent everything the credential owner can touch. This catalog lists the official Pylon MCP server, which uses OAuth. Running it behind the Speakeasy MCP Gateway adds SSO, role-based access, and an audit trail of every call.