> For the complete documentation index, see [llms.txt](https://docs.groundcover.com/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.groundcover.com/use-groundcover/connectors/pylon.md).

# Pylon

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

1. 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.
2. The Pylon admin enables **Settings → AI Controls → MCP Server** in Pylon.
3. A groundcover workspace admin goes to **Integrations → Connectors → Org Connectors**, selects **Pylon**, and enables it.
4. The admin clicks **Connect**, completes OAuth with an account that has **MCP Access**, and reviews the [tool restrictions](/use-groundcover/connectors/mcp.md#managing-tool-restrictions).
5. Each user goes to **Integrations → Connectors → My Connections**, selects **Pylon**, and clicks **Connect**.
6. 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.

{% hint style="info" %}
Agent Mode acts with the connected user's Pylon permissions, subject to groundcover's tool restrictions. Write actions may require approval.
{% endhint %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://docs.groundcover.com/use-groundcover/connectors/pylon.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.