@customer-support-success/pylon-mcp-server

Get the current authenticated user profile including name, email, role, and permissions.

Get all team members and support agents in your Pylon workspace.

Search for team members and support agents by name, email, or department.

Get customer contacts from Pylon. Returns contact details like name, email, and company.

Create a new customer contact in Pylon. Use carefully.

Search for customer contacts by name, email, company, or phone.

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.

Create a new support issue/ticket in Pylon.

Get complete details of a specific issue. Prefer this over message tools when you only need issue metadata.

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.

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.

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.

Search issues using structured filters; requires at least one filter. For unfiltered listing, use pylon_get_issues instead.

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.

Find issues from the same requestor as the source issue to identify recurring patterns.

Find issues from the same company/account to identify company-wide problems.

Find similar issues across all accounts to identify widespread issues or find past solutions.

Temporarily hide an issue until a future date/time for deferred follow-up.

Get an issue with its full conversation history. Prefer pylon_get_issue when you only need issue details.

Get the message history for an issue. Use when you need message content, not just issue metadata.

Get all knowledge bases in Pylon.

Create a new help article in a knowledge base.

Get all support teams in Pylon.

Get details of a specific support team including members and workload.

Create a new support team in Pylon.

Get all customer accounts from Pylon.

Get details of a specific customer account.

Get all available tags for categorizing issues and contacts.

Create a new tag for categorizing issues and contacts.

Get all ticket submission forms available to customers.

Get attachment metadata by ID. Use when you have an attachment_id from an issue message. Download the file using the returned URL.

Create a Pylon attachment by downloading a file from a public URL.

Link a Linear, Jira, GitHub, or Asana issue to a Pylon support issue for cross-system tracking.

Remove the link between a Pylon issue and an external ticketing system issue.

Get all users and contacts following a Pylon issue.

Add team members (user_ids) or customers (contact_ids) as followers to a Pylon issue.

Remove team members or customers from following a Pylon issue.

⚠️ Permanently delete a Pylon issue. This cannot be undone. Verify the correct issue ID before proceeding.