> For the complete documentation index, see [llms.txt](https://docs.usepylon.com/pylon-docs/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.usepylon.com/pylon-docs/agents/connectors.md).
# Connectors
Connect Pylon to any tool that you use
Connectors give Pylon agents access to external tools so they can search for context, retrieve information, and take action outside Pylon.
Connectors can expose tools through the Model Context Protocol (MCP) or a custom API. Administrators decide which connectors are available and which tools each agent can use.
### Connection types
| Connection | Best for | Identity used |
| ------------ | ---------------------------------------------------------------- | ---------------------------------------------------- |
| **Personal** | Assist Agent, Slack Agent, and other human-in-the-loop workflows | The individual teammate's external account |
| **Shared** | Team-wide or fallback access for human-in-the-loop workflows | An organization-level shared account or access token |
| **Agent** | Automations and other approved autonomous workflows | A dedicated agent or service account |
### Custom MCP server
Administrators add custom MCP connectors from the [Connectors](https://app.usepylon.com/settings/ai-controls/connectors) page. Once connected, MCP tools can be invoked from an agent, used by [Skills](/pylon-docs/agents/skills.md), or restricted to specific agents and roles.
If a system does not provide an MCP server, an administrator can define a [Custom API tool](https://app.usepylon.com/settings/ai-controls/connectors) that agents can use to call a public HTTP or HTTPS API endpoint. Private-network and loopback addresses are not supported.
### Permissions and data access
Connecting a tool does not automatically ingest all of that system's data into Pylon. It makes specific tools available for an agent to call when needed.
Pylon controls which tools agents can call. The connected system remains responsible for enforcing its own permissions and tenant boundaries.
{% hint style="info" %}
Admins can disable and enable tools globally directly on the connector level. Additionally, each agent has it's own tool configuration.
{% 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 by asking a question.
Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:
```
GET https://docs.usepylon.com/pylon-docs/agents/connectors.md?ask=&goal=
```
`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.
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.
