Pylon

Search and update Pylon support issues, accounts and contacts.

Add to Agentman Studio

Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.

Paste it into any MCP client. Setup docs

Resources

What the Pylon connector does

The Pylon MCP server connects Pylon — a B2B customer-support platform that tracks issues across Slack Connect, email, Microsoft Teams, chat and SMS — to Claude, ChatGPT and any MCP-compatible agent. Pylon documents eleven tools that search, read, create and update issues, accounts and contacts. Sign-in is OAuth only, and every action runs as you.

Verified connector

Listed by Anthropic as a partner connector in its Connectors Directory.

Connection checked by Agentman on .

Anthropic states this reflects the level of review a connector received, not a security audit.

Pylon tools (11)

  • create_issue
  • get_account
  • get_contact
  • get_issue
  • get_issue_messages
  • get_user
  • search_accounts
  • search_issues
  • update_account
  • update_issue

Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.

Limits

  • No application scopes exist. Pylon's authorization server advertises openid, profile, email and offline_access, all identity or session claims, and the server's RFC 9728 resource descriptor declares no scopes_supported at all. Nothing at the OAuth grant separates reading an issue from updating one. Your Pylon role is the only boundary, and Pylon's role table shows Members already hold write on issues, accounts and contacts.
  • The boundary that exists is a good one, and it is not in the OAuth layer. Pylon reserves deletion of accounts, contacts and issues for Admins, so an Admin who connects the server brings a delete-capable identity to it. No tool uses that capability today, but the separation lives in Pylon's roles rather than in anything the consent screen shows you.
  • We could not read tool schemas or safety annotations. The endpoint returned 401 to an anonymous request, so no parameter-level detail is published here and no tool's readOnlyHint could be confirmed.
  • Anthropic's directory under-lists by one tool. It shows ten; Pylon documents eleven. The gap is get_me. Anything a directory listing tells you about this server is a floor.
  • Rate limits apply per tool and per organization. Pylon states limits are enforced this way "to keep the MCP server healthy under bursty AI traffic" and that clients get a standard HTTP 429 when they hit one. Pylon does not publish the per-tool numbers for MCP. Its REST endpoints for the same objects are documented between 10 and 60 requests per minute, which suggests the order of magnitude without establishing it.
  • Sessions expire and the duration is not fixed. Pylon says some client sessions last hours and others several days, and that expiry can present as tools that stop returning results rather than as a visible error.
  • No API key authentication. OAuth only, which Pylon notes can rule out remote or headless environments.
  • Whether create_issue can contact a customer is unresolved. Pylon's REST create-issue endpoint can deliver the issue body to the requester by email, Slack, SMS, WhatsApp or in-app chat via destination_metadata. No published document says whether the MCP tool exposes that parameter, and the gated endpoint prevented us reading its schema. Treat it as unknown rather than as a no.
  • The tool count is the vendor's, not ours. Every count on this page comes from Pylon's documentation and Anthropic's directory. We ran no tools/list, because we hold no Pylon credentials and would not use them for this.

Frequently asked questions

Can the Pylon MCP connector send a reply to a customer?

No tool in Pylon's documented set posts a customer-facing reply. Pylon's REST API has a dedicated reply endpoint that sends a message visible to the requester, and the MCP server exposes no counterpart to it. The eleven tools search, read, create and update issues, accounts and contacts. Replying to a customer stays a dashboard or REST action.

How many tools does the Pylon MCP server have?

Pylon documents eleven and Anthropic's directory lists ten. The extra one is get_me, which returns the authenticated user and appears in Pylon's own table but not in the directory listing. Both lists agree on the other ten. We could not run a live handshake because the server requires OAuth, so eleven is the vendor's number.

What OAuth permissions does the Pylon MCP server request?

None that separate reading from writing. Pylon's authorization server advertised four scopes on 2026-08-22 — openid, profile, email and offline_access — and all four are identity or session claims. The consent screen therefore offers no way to grant searching issues without also granting updating them. Your Pylon role is the only real boundary.

Do I need a specific Pylon seat to connect the MCP server?

Yes. Pylon states you need a Member or Admin seat, and that Viewer and Integration users cannot authenticate and will see an Authorization failed error. Pylon also documents an MCP Access role permission that must be enabled for the user. If you hit the error, ask your workspace admin to change your seat type.

Can the Pylon connector see data I cannot see in Pylon?

No. Pylon states that access follows the same scoping as the dashboard, that the MCP server cannot return data the authenticated user cannot already see, and that it cannot perform writes the user cannot already make in the UI. Actions run on behalf of you, so your role and issue filters carry over unchanged.

Can the connector delete a Pylon issue or account?

Not with any documented tool. No name in the eleven carries a delete, merge, redact or archive verb, even though Pylon's REST API offers all four. Pylon also reserves deletion for Admins, so a Member's session could not delete regardless. Closing an issue is different and probably reachable through update_issue.

Why did my Pylon MCP session stop working?

OAuth sessions expire, and Pylon says the duration varies by client from a few hours to several days. Expired sessions surface as authentication errors or tools that quietly stop returning results. Re-authenticate the same way you first connected. Pylon calls this normal, and suggests contacting support if you reconnect several times a day.

Does the Pylon MCP server support API key authentication?

No. Pylon states the server only supports OAuth and that API key authentication is not currently available, which it notes may affect remote environments and platforms that cannot do OAuth for remote connections. Pylon's REST API does use bearer tokens, but that is a separate interface at a separate host.

Sources

More Communication connectors

  • AgentMail

    Give an AI agent its own email inbox: create inboxes, read threads and send mail to anyone.

  • Circleback

    Search meeting notes, transcripts, action items, calendar and connected email.

  • Fellow.ai

    Pull meeting transcripts, summaries, action items and participants from Fellow.

Browse all MCP connectorsClaude and ChatGPT setup guideBrowse AI skills

Product names and logos belong to their owners. Agentman is not affiliated with a connector's maker unless the page says the connector is built and run by Agentman.

Use it in an agent

Put Pylon to work.

Connect Pylon once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.

Open in Agentman Studio