Pylon MCP for AI agents
Agents read Pylon MCP at once. Changes and sends are held for a person's approval by default.
About Pylon MCP
Pylon is an AI-native B2B customer support platform that unifies ticketing, chat, knowledge base, and account intelligence across channels like Slack Connect, Microsoft Teams, email, and in-app chat.
What an agent can do in Pylon MCP
Every Pylon MCP action is classed by the platform as a read, a change or a send. Reads run at once. Changes and sends are held for a person by default.
Runs at once (reads)
Looks things up in Pylon MCP without asking first. 8 actions.
- Get accountGet full details for a Pylon customer account. Pass either the account ID (UUID) or external ID. Returns account details including name, domain, owner, tags, custom fields, and linked channels.
- Get contactGet full details for a Pylon contact (customer). Pass the contact ID (UUID). Returns contact details including name, email, account, and custom fields.
- Get issueGet full details for a Pylon support issue/ticket. Pass either the issue ID (UUID) or issue number. Returns title, body, state, metadata, custom fields, and nested account/assignee/requester info.
- Get issue messagesGet the full message history for a Pylon issue. Pass either the issue ID (UUID) or issue number. Returns all messages in chronological order with author info.
- Get meGet the currently authenticated user's details. Returns the user's name, email, role, and teams. No parameters required.
- Get userGet full details for a Pylon user (team member). Pass the user ID (UUID). Returns user details including name, email, role, and teams.
- Search accountsSearch for customer accounts in Pylon. Returns a lightweight summary of accounts matching the specified filters. Supports filtering by custom fields using the custom_field_filters parameter - pass the
- Search issuesSearch for issues/tickets in Pylon. Returns a lightweight summary of issues matching the specified filters. Supports cursor-based pagination - use the returned cursor to fetch additional pages. To get
Held for approval by default (changes and sends)
Held for a person's approval by default. The approval is recorded and the action is sent once, never twice, with 10 seconds to undo. 4 actions.
- Create issueCreate a new issue/ticket in Pylon. Requires an organization ID, account ID, title, and body HTML. Optionally specify requester, priority, assignee, team, and tags.
- Update accountUpdate an existing customer account in Pylon. You can update the name, owner, tags, and custom fields. Use the get_custom_fields tool with object_type 'account' to discover available custom field slug
- Update issueUpdate an existing issue/ticket in Pylon. You can update the state, assignee, team, and tags. Use the issue resource (issue://{issueId}) to get full issue details before updating.
- Upload account filesUpload one or more files (e.g. PDFs) into the Files tab of an account. Files with a matching filename are overwritten. Max 5 files per call, max 10 MB per file.
Changes wait in Needs you
Changes and sends in Pylon MCP are held for a person's approval by default. The approval is recorded, and the action is sent once, never twice, with 10 seconds to undo.
Related connectors
- Close MCP
- Customer.io MCP
- Intercom MCP
- AWS Marketplace MCP
- Better Stack MCP
- Carbon Voice MCP
Pylon MCP questions
Can an agent change data in Pylon MCP on its own?
Not by default. Changes and sends in Pylon MCP are held for a person's approval. The approval is recorded, and the action is sent once, never twice, with 10 seconds to undo.
What can an agent read in Pylon MCP?
This connector lists 8 read actions. Reads run at once, without waiting for approval.
How does Pylon MCP connect?
It connects with dcr oauth. Connectors are built and maintained by third-party developers; availability is confirmed during scoping.