Pylon MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PYLON_API_TOKEN | Yes | Your Pylon API token (can be generated from the Pylon dashboard at https://app.usepylon.com/settings/api-tokens, Admin users only) |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| pylon_get_organizationA | Get information about your Pylon organization |
| pylon_list_accountsA | List accounts. Returns compact table. Use pylon_get_account for details. |
| pylon_get_accountB | Get account details by ID. |
| pylon_create_accountC | Create a new account in Pylon |
| pylon_update_accountC | Update an existing account |
| pylon_delete_accountB | Delete an account |
| pylon_search_accountsC | Search accounts with filters. Returns compact table. |
| pylon_list_contactsC | List contacts. Returns compact table. |
| pylon_get_contactB | Get contact details by ID. |
| pylon_create_contactB | Create a new contact in Pylon |
| pylon_update_contactC | Update an existing contact |
| pylon_delete_contactA | Delete a contact |
| pylon_search_contactsC | Search contacts with filters. Returns compact table. |
| pylon_list_issuesA | List issues within a time range (max 30 days). Returns compact table. Use pylon_get_issue for details. |
| pylon_get_issueA | Get issue details by ID or number. Returns standard fields (no body). Use pylon_get_issue_body to fetch body content. |
| pylon_get_issue_bodyB | Get the full body content of an issue. Warning: can be very large for email threads. |
| pylon_create_issueC | Create a new issue/ticket in Pylon |
| pylon_update_issueC | Update an existing issue |
| pylon_delete_issueC | Delete an issue |
| pylon_search_issuesA | Search issues with filters. Returns compact table. Use pylon_get_issue for details. |
| pylon_snooze_issueA | Snooze an issue until a specific time |
| pylon_get_issue_followersB | Get the list of users following an issue |
| pylon_update_issue_followersB | Add or remove followers from an issue |
| pylon_redact_messageC | Redact a message from an issue |
| pylon_list_tagsC | List all tags in Pylon. |
| pylon_get_tagA | Get a specific tag by ID |
| pylon_create_tagC | Create a new tag |
| pylon_update_tagB | Update an existing tag |
| pylon_delete_tagC | Delete a tag |
| pylon_list_teamsC | List all teams in Pylon. |
| pylon_get_teamB | Get a specific team by ID |
| pylon_create_teamC | Create a new team |
| pylon_update_teamC | Update an existing team |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 33 tools
Each tool targets a specific entity and action (e.g., create_account, get_issue_body), with no overlapping purposes. Descriptions clearly differentiate between similar operations like list vs. search and get vs. get_body.
All tools follow a consistent verb_noun pattern with the pylon_ prefix, using snake_case throughout. Verbs are standard (create, get, list, search, update, delete) and applied uniformly.
33 tools is above the typical range but reasonable for a full-featured CRM/ticketing server. Each tool covers a distinct operation on entities like accounts, contacts, issues, tags, and teams.
The tool set provides full CRUD for all major entities, plus search, list, and specialized operations (redact, snooze, followers). There are no obvious gaps for the domain of customer support and account management.