Pylon MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PYLON_DEBUG | No | Set to 'true' to enable debug logging (optional). | |
| PYLON_API_TOKEN | Yes | Your Pylon API token | |
| PYLON_CACHE_TTL | No | Cache time-to-live in milliseconds (optional, default: 30000). Set to 0 to disable caching. | 30000 |
| PYLON_RETRY_MAX | No | Maximum retry attempts for transient failures (optional, default: 3). Set to 0 to disable retries. | 3 |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| pylon_get_me | Get the current authenticated user profile including name, email, role, and permissions. |
| pylon_get_users | Get all team members and support agents in your Pylon workspace. |
| pylon_search_users | Search for team members and support agents by name, email, or department. |
| pylon_get_contacts | Get customer contacts from Pylon. Returns contact details like name, email, and company. |
| pylon_create_contact | Create a new customer contact in Pylon. Use carefully. |
| pylon_search_contacts | Search for customer contacts by name, email, company, or phone. |
| pylon_get_issues | Get support issues within a time range (max 30 days); defaults to last 30 days. Use this for unfiltered listing. For filtering by state, tags, or custom statuses, use pylon_search_issues instead. |
| pylon_create_issue | Create a new support issue/ticket in Pylon. |
| pylon_get_issue | Get complete details of a specific issue. Prefer this over message tools when you only need issue metadata. |
| pylon_update_issue | Update an existing issue's title, description, status, priority, assignee, or tags. To add/remove tags without replacing all, use pylon_add_tags or pylon_remove_tags. |
| pylon_add_tags | Add tags to a Pylon issue without removing existing tags. To replace all tags, use pylon_update_issue; to remove tags, use pylon_remove_tags. |
| pylon_remove_tags | Remove specific tags from a Pylon issue without affecting other tags. To add tags, use pylon_add_tags; to replace all, use pylon_update_issue. |
| pylon_search_issues | Search issues using structured filters; requires at least one filter. For unfiltered listing, use pylon_get_issues instead. |
| pylon_search_issues_by_status | Search issues by status name, including custom statuses like "Waiting on Eng Input" or "Escalated". Automatically maps status names to state+tag combinations. For multi-filter searches, use pylon_search_issues instead. |
| pylon_find_similar_issues_for_requestor | Find issues from the same requestor as the source issue to identify recurring patterns. |
| pylon_find_similar_issues_for_account | Find issues from the same company/account to identify company-wide problems. |
| pylon_find_similar_issues_global | Find similar issues across all accounts to identify widespread issues or find past solutions. |
| pylon_snooze_issue | Temporarily hide an issue until a future date/time for deferred follow-up. |
| pylon_get_issue_with_messages | Get an issue with its full conversation history. Prefer pylon_get_issue when you only need issue details. |
| pylon_get_issue_messages | Get the message history for an issue. Use when you need message content, not just issue metadata. |
| pylon_get_knowledge_bases | Get all knowledge bases in Pylon. |
| pylon_create_knowledge_base_article | Create a new help article in a knowledge base. |
| pylon_get_teams | Get all support teams in Pylon. |
| pylon_get_team | Get details of a specific support team including members and workload. |
| pylon_create_team | Create a new support team in Pylon. |
| pylon_get_accounts | Get all customer accounts from Pylon. |
| pylon_get_account | Get details of a specific customer account. |
| pylon_get_tags | Get all available tags for categorizing issues and contacts. |
| pylon_create_tag | Create a new tag for categorizing issues and contacts. |
| pylon_get_ticket_forms | Get all ticket submission forms available to customers. |
| pylon_get_attachment | Get attachment metadata by ID. Use when you have an attachment_id from an issue message. Download the file using the returned URL. |
| pylon_create_attachment_from_url | Create a Pylon attachment by downloading a file from a public URL. |
| pylon_link_external_issue | Link a Linear, Jira, GitHub, or Asana issue to a Pylon support issue for cross-system tracking. |
| pylon_unlink_external_issue | Remove the link between a Pylon issue and an external ticketing system issue. |
| pylon_get_issue_followers | Get all users and contacts following a Pylon issue. |
| pylon_add_issue_followers | Add team members (user_ids) or customers (contact_ids) as followers to a Pylon issue. |
| pylon_remove_issue_followers | Remove team members or customers from following a Pylon issue. |
| pylon_delete_issue | ⚠️ Permanently delete a Pylon issue. This cannot be undone. Verify the correct issue ID before proceeding. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/mgmonteleone/pylon-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server