Pylon MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PYLON_API_TOKEN | Yes | Pylon API token |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| pylon_list_accountsA | List all accounts in Pylon with optional pagination. |
| pylon_get_accountA | Get a specific account by its ID. |
| pylon_create_accountB | Create a new account in Pylon. |
| pylon_update_accountC | Update an existing account in Pylon. |
| pylon_list_issuesB | List issues within a time range in Pylon. |
| pylon_get_issueA | Get a specific issue by its ID. |
| pylon_create_issueC | Create a new issue in Pylon. |
| pylon_update_issueC | Update an existing issue in Pylon. |
| pylon_search_issuesA | Search issues in Pylon using filters. Supports complex queries with AND/OR operators and nested filters. Common filter fields: state, priority, assignee_id, account_id, tags, requester.email, source, team_id. |
| pylon_get_issue_messagesB | Get all messages for a specific issue. |
| pylon_redact_messageB | Redact a specific message in an issue. |
| pylon_link_external_issueA | Link or unlink external issues (from Linear, Asana, Jira, or GitHub) to/from a Pylon issue. |
| pylon_list_custom_fieldsA | List all custom fields for a specific object type. |
| pylon_get_custom_fieldA | Get a specific custom field by its ID. |
| pylon_create_custom_fieldB | Create a new custom field in Pylon. |
| pylon_update_custom_fieldB | Update an existing custom field in Pylon. |
| pylon_create_taskB | Create a new task in Pylon. Rate limit: 60 requests per minute. |
| pylon_update_taskB | Update an existing task in Pylon. Rate limit: 60 requests per minute. |
| pylon_delete_taskB | Delete an existing task in Pylon. Rate limit: 20 requests per minute. |
| pylon_create_projectB | Create a new project in Pylon. Rate limit: 60 requests per minute. |
| pylon_update_projectB | Update an existing project in Pylon. Rate limit: 60 requests per minute. |
| pylon_delete_projectA | Delete an existing project in Pylon. Rate limit: 20 requests per minute. |
| pylon_create_milestoneB | Create a new milestone in Pylon. Rate limit: 60 requests per minute. |
| pylon_update_milestoneB | Update an existing milestone in Pylon. Rate limit: 60 requests per minute. |
| pylon_delete_milestoneA | Delete an existing milestone in Pylon. Rate limit: 60 requests per minute. |
| pylon_list_knowledge_basesA | List all knowledge bases for the organization. |
| pylon_get_knowledge_baseA | Get a specific knowledge base by its ID. |
| pylon_list_articlesA | List all articles in a knowledge base with optional pagination. |
| pylon_get_articleA | Get a specific article by its ID within a knowledge base. |
| pylon_create_articleC | Create a new article within a knowledge base. |
| pylon_update_articleA | Update an existing article in a knowledge base. Only provided fields are modified. |
| pylon_delete_articleA | Permanently delete an article from a knowledge base. |
| pylon_list_collectionsA | List all collections in a knowledge base. |
| pylon_get_collectionA | Get a specific collection by its ID within a knowledge base. |
| pylon_create_collectionB | Create a new collection within a knowledge base. |
| pylon_create_route_redirectA | Create a path redirect within a knowledge base, mapping a source path to an article or collection. |
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 36 tools
Each tool targets a distinct resource-action combination (e.g., account, issue, article). Overlapping concepts like list_issues vs search_issues are clearly differentiated by scope (time range vs complex filters). No two tools appear to do the same thing.
All tools follow a consistent 'pylon_verb_noun' pattern with snake_case verbs (list, get, create, update, delete, search). The naming is predictable and uniform across all resources.
At 36 tools, the set is substantially larger than typical MCP servers. While it covers multiple resource types, many resources (projects, tasks, milestones) lack corresponding list/get tools, making the count feel inflated rather than comprehensive.
Major gaps exist: projects, tasks, and milestones have create/update/delete but no list/get operations, leaving no way to retrieve them. Custom fields lack delete, and collections lack update/delete. These are critical CRUD omissions.