# Pylon MCP AI integration on Definable

> 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 this connects

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.

Vendor: https://mcp.usepylon.com

## Tools available

**12** tools available. First 12:

- `PYLON_MCP_CREATE_ISSUE` — Create issue — Create a new issue/ticket in Pylon. Requires an organization ID, account ID, title, and body HTML. Optionally specify requester, priority, assignee, team, and tags.
- `PYLON_MCP_GET_ACCOUNT` — Get account — Get 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.
- `PYLON_MCP_GET_CONTACT` — Get contact — Get full details for a Pylon contact (customer). Pass the contact ID (UUID). Returns contact details including name, email, account, and custom fields.
- `PYLON_MCP_GET_ISSUE` — Get issue — Get 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.
- `PYLON_MCP_GET_ISSUE_MESSAGES` — Get issue messages — Get 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.
- `PYLON_MCP_GET_ME` — Get me — Get the currently authenticated user's details. Returns the user's name, email, role, and teams. No parameters required.
- `PYLON_MCP_GET_USER` — Get user — Get full details for a Pylon user (team member). Pass the user ID (UUID). Returns user details including name, email, role, and teams.
- `PYLON_MCP_SEARCH_ACCOUNTS` — Search accounts — Search 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 custom field slug as the field name. For user-type custom fields (e.g. Salesforce AE owner), you can pass a Pylon user name or user ID as the value. Supports cursor-based pagination - use the returned cursor to fetch additional pages. To get full account details including custom fields, external IDs, and linked channels, use the account resource: account://{accountId}
- `PYLON_MCP_SEARCH_ISSUES` — Search issues — Search 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 full issue details including body, custom fields, and nested account/assignee/requester info, use the issue resource: issue://{issueId}
- `PYLON_MCP_UPDATE_ACCOUNT` — Update account — Update 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 slugs. Use the get_account tool to get full account details before updating.
- `PYLON_MCP_UPDATE_ISSUE` — Update issue — Update 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.
- `PYLON_MCP_UPLOAD_ACCOUNT_FILES` — Upload account files — Upload 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.

## Auth

Auth schemes: `DCR_OAUTH`.

## How agents use Pylon MCP

Inside a Definable workflow, Pylon MCP is one of the tools the **Distributor specialist** can call. Example coordination patterns:

- **Researcher → Pylon MCP** — the Researcher (GPT-5.5) pulls context from Pylon MCP (records, threads, documents), synthesises findings, and briefs the rest of the team.
- **Writer → Distributor → Pylon MCP** — the Writer (Claude Opus 4.7) drafts copy in brand voice, the Verifier passes it, then the Distributor writes the result into Pylon MCP (create record, post message, draft email).
- **Designer / Engineer → Distributor → Pylon MCP** — the Designer ships an asset or the Engineer ships a code change, the Distributor delivers it via Pylon MCP (attach file, open PR comment, post status).

The Verifier checks every Pylon MCP call. On rate limit, schema drift, or auth refresh it self-heals and retries — the workflow completes without manual intervention.

## Categories

- model context protocol — https://definable.ai/apps/category/model-context-protocol/
- crm — https://definable.ai/apps/category/crm/
- communication — https://definable.ai/apps/category/communication/
- it operations — https://definable.ai/apps/category/it-operations/

## Related

- HTML page: https://definable.ai/apps/pylon_mcp/
- Same category (model context protocol): https://definable.ai/apps/category/model-context-protocol/
- All integrations: https://definable.ai/apps/
- Workflow (multi-agent loop): https://definable.ai/workflow/
- Apps llms.txt index: https://definable.ai/llms-apps.txt