Connectors

Connect Pylon to any tool that you use

This feature is currently in beta, with access limited to those participating in the beta.

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	Background Agent and approved autonomous workflows	A dedicated agent or service account

Custom MCP server

Administrators add custom MCP connectors from the Connectors page. Once connected, MCP tools can be invoked from an agent, used by Skills, or restricted to specific agents and roles.

If a system does not provide an MCP server, an administrator can define a Custom API tool that agents can use to hit internal or third party API endpoints.

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.

Admins can disable and enable tools globally directly on the connector level and each agent has it's own tool configuration under