Claude MarketplacesSubmit
justinbeckwith avatar

Pylon Mcp

justinbeckwith/pylon-mcp

Connects Claude to the Pylon customer support platform with full CRUD operations across accounts, contacts, issues, teams, and tags. You get search and filtering on accounts, contacts, and issues, plus issue-specific actions like snoozing tickets, managing followers, and redacting messages. Requires a Pylon API token with admin access. Useful when you want Claude to help triage support queues, update customer records, create tickets from conversations, or pull context from your Pylon data without switching windows. Covers the core Pylon API surface including organization details and team management.

GitHub stars
4
tools
29
transport
STDIO
last updated
Apr 2, 2026
View on GitHub

Tools

29 tools

Public tool metadata for what this MCP can expose to an agent.

pylon_get_meGet 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.

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.

No parameter schema in public metadata yet.

pylon_get_contactsGet 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.2 params

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.

Parameters* required
limitnumber
Maximum number of contacts to return (1-100). Default is 20. Example: 50
searchstring
Search contacts by name, email, or company. Examples: "john@example.com", "Acme Corp", "John Smith"
pylon_create_contactCreate a new customer contact in Pylon. Use this when adding a new customer who will submit support requests or access your customer portal.3 params

Create a new customer contact in Pylon. Use this when adding a new customer who will submit support requests or access your customer portal.

Parameters* required
emailstring
Contact email address. Must be valid email format. Example: "sarah@company.com"
namestring
Full name of the contact. Example: "Sarah Johnson"
portal_rolestring
Role in customer portal: "admin", "member", "viewer". Determines access level. Example: "member"
pylon_get_issuesGet 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.3 params

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.

Parameters* required
assigneestring
Filter by assigned team member. Use email or user ID. Examples: "john@support.com", "user_123"
limitnumber
Maximum number of issues to return (1-100). Default is 50. Example: 25
statusstring
Filter by issue status. Options: "open", "in_progress", "pending", "resolved", "closed". Example: "open"
pylon_create_issueCreate 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.5 params

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.

Parameters* required
assigneestring
Team member to assign (optional). Use email or user ID. Example: "support@company.com"
descriptionstring
Detailed description of the issue, including steps to reproduce and impact. Example: "User reports that clicking login button shows error message. Affects all Chrome users on Windows."
prioritystring
Priority level: "low", "medium", "high", "urgent". Example: "high"
statusstring
Initial status: "open", "in_progress", "pending", "resolved", "closed". Usually "open" for new issues. Example: "open"
titlestring
Brief title describing the issue. Examples: "Login page not loading", "Cannot upload files", "Billing question"
pylon_get_knowledge_basesGet 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.

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.

No parameter schema in public metadata yet.

pylon_get_knowledge_base_articlesGet 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.1 params

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.

Parameters* required
knowledge_base_idstring
ID of the knowledge base to get articles from. Get this from pylon_get_knowledge_bases first. Example: "kb_123abc"
pylon_create_knowledge_base_articleCreate 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.3 params

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.

Parameters* required
contentstring
Full article content in markdown or HTML format. Include step-by-step instructions, screenshots, and links. Example: "## Steps to Reset Password 1. Go to login page 2. Click Forgot Password..."
knowledge_base_idstring
ID of the knowledge base to add article to. Example: "kb_123abc"
titlestring
Article title that clearly describes the topic. Examples: "How to Reset Your Password", "Troubleshooting Login Issues", "Billing FAQ"
pylon_get_teamsGet 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.

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.

No parameter schema in public metadata yet.

pylon_get_teamGet detailed information about a specific support team. Returns team members, their roles, current workload, and team performance metrics.1 params

Get detailed information about a specific support team. Returns team members, their roles, current workload, and team performance metrics.

Parameters* required
team_idstring
ID of the team to get details for. Get this from pylon_get_teams first. Example: "team_456def"
pylon_create_teamCreate 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).3 params

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).

Parameters* required
descriptionstring
Description of team responsibilities and expertise. Example: "Handles complex technical issues, API questions, and integration support"
membersarray
Array of user IDs or emails of team members. Example: ["john@company.com", "user_123", "sarah@company.com"]
namestring
Team name that describes their specialization. Examples: "Technical Support", "Billing Team", "Enterprise Support", "Level 2 Support"
pylon_get_accountsGet 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.

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.

No parameter schema in public metadata yet.

pylon_get_accountGet detailed information about a specific customer account. Returns company details, subscription info, billing status, and associated contacts and issues.1 params

Get detailed information about a specific customer account. Returns company details, subscription info, billing status, and associated contacts and issues.

Parameters* required
account_idstring
ID of the account to get details for. Get this from pylon_get_accounts or customer records. Example: "acc_789xyz"
pylon_search_usersSearch for team members and support agents in Pylon. Use this to find colleagues by name, email, or department when assigning issues or checking availability.1 params

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.

Parameters* required
querystring
Search term to find users by name, email, or department. Examples: "john", "support@company.com", "technical team"
pylon_get_usersGet all team members and support agents in your Pylon workspace. Returns user profiles including names, roles, teams, and availability status.

Get all team members and support agents in your Pylon workspace. Returns user profiles including names, roles, teams, and availability status.

No parameter schema in public metadata yet.

pylon_search_contactsSearch 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.1 params

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.

Parameters* required
querystring
Search term to find contacts. Can search by name, email, company, or phone. Examples: "alice@example.com", "Acme Corporation", "John Smith", "+1-555-0123"
pylon_search_issuesSearch 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.2 params

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.

Parameters* required
filtersobject
Additional filters as key-value pairs. Examples: {"status": "open", "priority": "high"}, {"assignee": "john@company.com", "created_after": "2024-01-01"}
querystring
Search term to find issues. Can search in titles, descriptions, and customer names. Examples: "login error", "billing question", "API timeout", "John Smith"
pylon_get_issueGet complete details of a specific support issue/ticket. Returns full issue information including title, description, status, priority, assignee, customer info, and conversation history.1 params

Get complete details of a specific support issue/ticket. Returns full issue information including title, description, status, priority, assignee, customer info, and conversation history.

Parameters* required
issue_idstring
ID of the issue to retrieve. Get this from pylon_get_issues or pylon_search_issues. Example: "issue_abc123"
pylon_update_issueUpdate 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.6 params

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.

Parameters* required
assigneestring
New assignee email or user ID. Example: "tech-lead@company.com"
descriptionstring
Updated description with new information or resolution details. Example: "Fixed CSS conflict causing login button to not render properly."
issue_idstring
ID of the issue to update. Example: "issue_abc123"
prioritystring
New priority level: "low", "medium", "high", "urgent". Example: "medium"
statusstring
New status: "open", "in_progress", "pending", "resolved", "closed". Example: "resolved"
titlestring
New title for the issue. Example: "RESOLVED: Login page not loading"
pylon_snooze_issueTemporarily 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).2 params

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).

Parameters* required
issue_idstring
ID of the issue to snooze. Example: "issue_abc123"
untilstring
Date and time when issue should reappear (ISO 8601 format). Examples: "2024-01-15T09:00:00Z" (specific date/time), "2024-01-20T00:00:00Z" (beginning of day)
pylon_get_issue_messagesGet 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.1 params

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.

Parameters* required
issue_idstring
ID of the issue to get messages for. Example: "issue_abc123"
pylon_create_issue_messageAdd a new message/reply to a support issue conversation. Use this to respond to customers, add internal notes, or provide updates on issue progress.2 params

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.

Parameters* required
contentstring
Message text to send. Can include formatting and links. Examples: "Hi John, I've escalated this to our dev team. You should see a fix by tomorrow.", "**Internal note:** This appears to be related t...
issue_idstring
ID of the issue to add message to. Example: "issue_abc123"
pylon_get_tagsGet 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").

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").

No parameter schema in public metadata yet.

pylon_create_tagCreate a new tag for categorizing issues and contacts. Use this to add new categories that help organize and filter your support tickets effectively.2 params

Create a new tag for categorizing issues and contacts. Use this to add new categories that help organize and filter your support tickets effectively.

Parameters* required
colorstring
Color for the tag in hex format or color name. Examples: "#FF0000", "red", "#00AA00", "blue"
namestring
Tag name that describes the category. Examples: "billing-question", "feature-request", "bug-report", "urgent", "enterprise-customer"
pylon_get_ticket_formsGet 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).

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).

No parameter schema in public metadata yet.

pylon_create_ticket_formCreate 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).3 params

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).

Parameters* required
descriptionstring
Description shown to customers explaining when to use this form. Example: "Use this form to report bugs or technical issues with our software."
fieldsarray
Array of form field objects defining what information to collect. Example: [{"type": "text", "name": "summary", "required": true}, {"type": "textarea", "name": "steps_to_reproduce"}, {"type": "sele...
namestring
Form name that describes its purpose. Examples: "Bug Report Form", "Billing Inquiry", "Feature Request", "Technical Support"
pylon_get_webhooksGet all configured webhooks in Pylon. Webhooks automatically send notifications to external systems when events occur (e.g., new issues created, status changes, messages added).

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).

No parameter schema in public metadata yet.

pylon_create_webhookCreate 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.3 params

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.

Parameters* required
activeboolean
Whether webhook should start active immediately. Default is true. Example: true
eventsarray
Array of events to trigger webhook. Examples: ["issue.created", "issue.updated", "issue.resolved"], ["message.created"], ["contact.created", "team.assigned"]
urlstring
HTTPS URL where webhook payloads will be sent. Must be publicly accessible. Examples: "https://hooks.slack.com/services/...", "https://api.myapp.com/webhooks/pylon"
pylon_delete_webhookDelete an existing webhook to stop sending notifications to an external system. Use this when removing integrations or cleaning up unused webhooks.1 params

Delete an existing webhook to stop sending notifications to an external system. Use this when removing integrations or cleaning up unused webhooks.

Parameters* required
webhook_idstring
ID of the webhook to delete. Get this from pylon_get_webhooks. Example: "webhook_xyz789"

Sponsors

Promote your product hereReach 125k+ visitors monthlyPromote your product hereReach 125k+ visitors monthlyAgent CaffeineSponsoredClose your lid, come back to finished workSnugSponsoredThe clipboard manager for the AI eraPromote your product hereReach 125k+ visitors monthlyWaxSponsoredBlock anything with supervision, without erasing your iPhonePromote your product hereReach 125k+ visitors monthlyknobsSponsoredSee your site on any phone, any day, in any language

Readme

pylon-mcp

pylon-mcp

MCP (Model Context Protocol) server for Pylon customer support platform.

Installation

corepack enable
pnpm install
pnpm run build

Configuration

  1. Copy the example environment file:

    cp .env.example .env

  2. Edit .env and add your Pylon API token:

    PYLON_API_TOKEN=your_api_token_here

You can generate an API token from the Pylon dashboard. Note: Only Admin users can create API tokens.

Usage

With Claude Desktop

Add to your Claude Desktop configuration (~/Library/Application Support/Claude/claude_desktop_config.json on macOS):

{
  "mcpServers": {
    "pylon": {
      "command": "node",
      "args": ["--env-file", "/path/to/pylon-mcp/.env", "/path/to/pylon-mcp/dist/index.js"]
    }
  }
}

With Claude Code

Add to your Claude Code MCP settings:

View the full README on GitHub

Details

Repository
github.com/justinbeckwith/pylon-mcp
Package
pylon-mcp
Transport
STDIO
Registry
MCP registry, active

More from justinbeckwith