Pylon
Connect Pylon to investigate customer issues and take support actions from Agent Mode
Connect Pylon to give Agent Mode customer context during an investigation and let it turn technical findings into support work.
What You Can Do
Read and investigate
Find open Pylon issues mentioning checkout timeouts, group them by customer and priority, and summarize the common symptoms.
Read the latest conversation for this account and show me the relevant knowledge-base guidance before I respond.
Take action
Create a high-priority Pylon issue for the customer impact shown in this monitor investigation. Include the affected service, evidence, and investigation link, then assign it to the support engineering team.
Add an internal note with the root cause and workaround to the related issue, then move it to waiting on customer.
Available actions depend on the tools and permissions enabled for the connection. They can include creating, assigning, and updating issues as well as adding customer-facing or internal context.
Setup
A Pylon admin grants MCP Access to the Member or Admin account that will authorize the groundcover organization connection, and to every user who will create a personal connection. Viewer and Integration accounts cannot connect.
The Pylon admin enables Settings → AI Controls → MCP Server in Pylon.
A groundcover workspace admin goes to Integrations → Connectors → Org Connectors, selects Pylon, and enables it.
The admin clicks Connect, completes OAuth with an account that has MCP Access, and reviews the tool restrictions.
Each user goes to Integrations → Connectors → My Connections, selects Pylon, and clicks Connect.
Complete the Pylon OAuth flow with a Pylon Member or Admin account that has MCP Access.
Without MCP Access, authorization fails and Agent Mode cannot discover Pylon tools.
Agent Mode acts with the connected user's Pylon permissions, subject to groundcover's tool restrictions. Write actions may require approval.
Last updated