Ask questions about your accounts, issues, and contacts in natural language, and let Claude pull live Pylon data to surface patterns across your customer base.
Look up any customer and bring their accounts, tickets, and history into the conversation, so your analysis draws on current data instead of stale exports.
Blend Pylon data with other connected tools like Notion and Linear to run richer ad-hoc analysis and cross-reference customer context in one place.
Click the "+" button in the lower left corner of your chat or type "/" to open the menu.
Select Browse connectors to open the directory where you can browse by category or scroll the full list. Click on the Pylon connector and click "Connect" or "Install" to begin.
A standard OAuth window opens. You sign in with your existing account credentials.
Pylon connects to Claude via its MCP server. You authenticate using OAuth with your Pylon account, and the connection gives Claude access to your Pylon data on your behalf.
Common workflows include debugging a customer issue end-to-end. For example, prompting Claude Code with "debug this..." and opening a PR for a bug fix. Or writing a product spec in Notion by feeding Claude a set of related Pylon issues and generating a spec doc based on real customer evidence. You can also query account health, look up open issues by customer, or summarize support trends across your accounts.
Claude can both read and update issues, accounts, and contacts within the data your Pylon account can see. All actions are performed on your behalf, and access is scoped to exactly what you can already see and edit in the Pylon dashboard.
A Member or Admin seat is required. Viewer and Integration users cannot authenticate and will see an "Authorization failed" error. Ask your workspace admin to upgrade your seat type in Settings, then Users. Note that the Pylon MCP server only supports OAuth authentication. API key authentication is not currently available.
Rate limits are applied per tool and per organization to keep the MCP server healthy under bursty AI traffic. Clients receive a standard 429 response when limits are hit. If you're running automated Claude Code pipelines that call Pylon tools in rapid succession, consider adding delays between calls or batching your queries to avoid hitting limits.
Pylon connects with the tools your team lives in — Slack, email, CRMs, ticketing systems,and more. Meet your customers where they are and streamline every support workflow.
Receive and respond to customer messages from Telegram
Manage B2B support directly in Slack channels alongside your team.
Connect Pylon to Granola to ingest call recordings
Sync Outlook Calendar meetings to customer records in Pylon
Automatically capture and log Google Meet call notes to Pylon
Automcatically link active incidents to affected customer conversations.
Enrich customer records with usage data from Amazon Redshift.
Create Shortcut stories from customer conversations automatically
Trigger PagerDuty incidents from critical customer-reported issues.
