Skip to main content
Activation required. AI access management must be enabled for your tenant before you can use it. To get started, contact the C1 support team for a walkthrough.
C1 can govern Pylon access two ways. Both let your AI clients read from and act on Pylon through governed MCP tools, but they come from different places and appear as two separate entries in your MCP server catalog:
  • Pylon MCP — listed as plain Pylon in your catalog. C1 registers Pylon’s own hosted MCP server (mcp.usepylon.com) as a downstream server C1 governs. Authentication is always per-user OAuth using dynamic client registration (DCR) — Pylon’s hosted MCP server doesn’t support a bearer token or API key, so there’s no integration to create in Pylon first. Tool calls run with the connected user’s own Pylon seat permissions.
  • Pylon API — C1 hosts its own MCP server that translates Pylon’s REST API into tools. Authentication is a single shared bearer token (an API token generated in Pylon), so every tool call reaches Pylon as one shared identity.
Use the native Pylon MCP option (listed as plain Pylon in your catalog) if per-user OAuth is acceptable for your tenant and Pylon’s own agentic tool set is enough. Use Pylon API if you need a shared service-account credential (bearer token) instead.
C1 registers as a client of Pylon’s own hosted MCP server (Pylon MCP) rather than translating Pylon’s REST API itself. Your users’ AI clients still only ever see C1-governed MCP tools, but C1 proxies each tool call straight through to mcp.usepylon.com under the connected user’s authorized session, then returns the result. The tools available are exactly the ones Pylon’s own MCP server exposes — C1 doesn’t reshape or add to them.

​
Before you begin

  • AI access management must be enabled for your tenant. See Enable AI access management.
  • Nothing to create in Pylon ahead of time. This option only supports per-user OAuth with dynamic client registration — Pylon’s hosted MCP server doesn’t offer a bearer token or API key mode, so there’s no client ID, secret, or integration to register.
  • A Pylon admin must first turn on the MCP server from Settings → AI Controls → MCP Server in the Pylon dashboard (Pylon MCP). Each person who will connect needs a Member or Admin seat with the MCP Access role enabled; Viewer and Integration seats can’t authenticate and see an “Authorization failed” error (Connecting to the Pylon MCP Server).
In your MCP server catalog, this option is listed as Pylon — distinct from the Pylon API entry, which connects through C1’s own MCP server. If you don’t see either, contact the C1 support team to enable it for your tenant.

​
Set up per-user OAuth

Per-user OAuth with dynamic client registration (DCR) is the only authentication method this option supports — there’s no bearer token or API key fallback. Each user authorizes individually, and C1 registers itself with Pylon’s authorization server automatically, so there’s no app to create in Pylon first.
1
Follow Register an MCP server and select Pylon from the catalog.
2
When you configure authentication, choose OAuth2 — per-user passthrough and enable Use dynamic client registration. There’s no client ID or secret to enter.
3
Save your changes. The first time a user calls a Pylon tool from their AI client, they’re redirected to Pylon to sign in (if they aren’t already) and approve the connection, then returned to C1.

​
What access is granted

Once a user authorizes, tool calls run with that user’s own Pylon seat permissions — they can search for and read issues, accounts, and contacts they can already see in Pylon, and create or update them on the same terms as in the Pylon dashboard (Pylon MCP). The MCP server never returns data the user can’t already see, or performs a write the user can’t already make, in Pylon.

​
How Pylon MCP credentials are shared

This option only supports per-user OAuth — there’s no shared, service-account, or bearer-token mode. Every tool call runs under the calling user’s own Pylon identity, and Pylon attributes each action to that individual. C1 still attributes each call to the individual user in the AI tool usage audit log.

​
Discover and govern tools

After you register the server, C1 runs tool discovery against Pylon’s MCP server. Discovered tools appear on the server’s Tools tab and include Pylon’s own search, read, create, and update tools for issues, accounts, and contacts.Each tool starts as either Pending review or automatically Approved, depending on the option chosen when the server was set up or your tenant’s default tool settings in AI > MCP > Settings. See Require tool approval and Default tool classification.Before anyone can call a Pylon tool, it must be approved, added to a toolset, and bound to an access profile. Continue to Govern tools and toolsets to set this up.
Tool discovery runs even if authentication isn’t complete yet, so seeing discovered tools doesn’t confirm a user has authorized. You confirm access when an approved user successfully calls a Pylon tool from their AI client.

​
Manage access to Pylon MCP

Because this option uses per-user OAuth, there’s no shared secret in C1 to rotate. Users and admins manage access from Pylon itself:
  • An individual user’s session expires periodically — some sessions last a few hours, others several days (Connecting to the Pylon MCP Server). Reconnecting re-runs the same authorization flow.
  • A Pylon admin can turn off the integration workspace-wide from the same Settings → AI Controls → MCP Server panel used to enable it, or remove an individual’s MCP Access role from the Users page under Settings to cut off just that person’s connection (Roles & User Management).