Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PYLON_API_TOKEN | Yes | Your Pylon API token (required) |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| pylon_get_me | Get current user information from Pylon. Returns your user profile including name, email, role, and permissions. Use this to verify your authentication and see what access level you have. |
| pylon_get_contacts | Get customer contacts from Pylon. Use this to find customers who have submitted support tickets or inquiries. Returns contact details like name, email, company, and contact history. |
| pylon_create_contact | Create a new customer contact in Pylon. Use this when adding a new customer who will submit support requests or access your customer portal. |
| pylon_get_issues | Get support issues/tickets from Pylon. Returns a list of customer support requests with details like title, status, priority, and assigned team member. Use this to see your workload or find specific issues. |
| pylon_create_issue | Create a new support issue/ticket in Pylon. Use this to log customer problems, bug reports, or feature requests that need to be tracked and resolved. |
| pylon_get_knowledge_bases | Get all knowledge bases from Pylon. Knowledge bases contain help articles, FAQs, and documentation that customers can access. Returns list of available knowledge bases with their names and article counts. |
| pylon_get_knowledge_base_articles | Get help articles from a specific knowledge base. Use this to find existing documentation that might help resolve customer issues or to see what self-service content is available. |
| pylon_create_knowledge_base_article | Create a new help article in a knowledge base. Use this to add new documentation, FAQs, or troubleshooting guides that customers can access for self-service support. |
| pylon_get_teams | Get all support teams from Pylon. Teams are groups of support agents that handle different types of issues (e.g., Technical, Billing, Sales). Returns team names, member counts, and specializations. |
| pylon_get_team | Get detailed information about a specific support team. Returns team members, their roles, current workload, and team performance metrics. |
| pylon_create_team | Create a new support team in Pylon. Use this to organize support agents into specialized groups for handling different types of customer issues (e.g., Technical Support, Billing, Enterprise accounts). |
| pylon_get_accounts | Get all customer accounts from Pylon. Accounts represent companies or organizations that use your service. Returns account details like company name, subscription level, and contact information. |
| pylon_get_account | Get detailed information about a specific customer account. Returns company details, subscription info, billing status, and associated contacts and issues. |
| pylon_search_users | Search for team members and support agents in Pylon. Use this to find colleagues by name, email, or department when assigning issues or checking availability. |
| pylon_get_users | Get all team members and support agents in your Pylon workspace. Returns user profiles including names, roles, teams, and availability status. |
| pylon_search_contacts | Search for customer contacts in Pylon by name, email, company, or other details. Use this to quickly find a specific customer when you need to view their information or create an issue for them. |
| pylon_search_issues | Search for support issues/tickets in Pylon by keywords, customer name, or issue content. Use this to find related issues, check for duplicates, or research similar problems. |
| pylon_get_issue | Get complete details of a specific support issue/ticket. Returns full issue information including title, description, status, priority, assignee, customer info, and conversation history. |
| pylon_update_issue | Update an existing support issue/ticket. Use this to change status (e.g., mark as resolved), reassign to different team members, update priority, or modify details as you work on the issue. |
| pylon_snooze_issue | Temporarily hide an issue until a future date/time. Use this for issues that cannot be worked on now but need follow-up later (e.g., waiting for customer response, scheduled maintenance, feature release). |
| pylon_get_issue_messages | Get the conversation history for a specific support issue. Returns all messages between customer and support team, including timestamps and sender information. Use this to understand the context and progress of an issue. |
| pylon_create_issue_message | Add a new message/reply to a support issue conversation. Use this to respond to customers, add internal notes, or provide updates on issue progress. |
| pylon_get_tags | Get all available tags for categorizing issues and contacts. Tags help organize and filter support tickets by topic, urgency, or type (e.g., "bug", "feature-request", "billing", "urgent"). |
| pylon_create_tag | Create a new tag for categorizing issues and contacts. Use this to add new categories that help organize and filter your support tickets effectively. |
| pylon_get_ticket_forms | Get all ticket submission forms available to customers. Forms define what information customers provide when creating new support requests (e.g., bug report form, billing inquiry form). |
| pylon_create_ticket_form | Create a new ticket submission form for customers. Use this to customize what information customers provide when creating different types of support requests (bug reports, feature requests, billing questions). |
| pylon_get_webhooks | Get all configured webhooks in Pylon. Webhooks automatically send notifications to external systems when events occur (e.g., new issues created, status changes, messages added). |
| pylon_create_webhook | Create a new webhook to automatically notify external systems when events occur in Pylon. Use this to integrate with Slack, Discord, email systems, or custom applications. |
| pylon_delete_webhook | Delete an existing webhook to stop sending notifications to an external system. Use this when removing integrations or cleaning up unused webhooks. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |