Pylon for AI agents
Pylon is an AI-native B2B customer support platform unifying ticketing, chat, and account intelligence across Slack, Teams, and email. Support teams use it to manage every customer conversation in one place. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.
What agents do in Pylon.
Create a support issue
Open a new issue from a customer conversation so it gets tracked and assigned.
Check an account's open issues read-only
Look up an account's issue history before responding to a new escalation.
Update an issue with approval
Change an issue's status or owner only after a support lead confirms the update.
12 Pylon actions, graded by risk.
Every Pylon action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.
read
8Look things up. Allowed by default.
- pylon.get_meGet me
- pylon.get_userGet user
- pylon.get_issueGet issue
- pylon.get_accountGet account
- pylon.get_contactGet contact
- pylon.search_issuesSearch issues
- pylon.search_accountsSearch accounts
- pylon.get_issue_messagesGet issue messages
write
4Create and change things. Allow, or ask the user first.
- pylon.create_issueCreate issue
- pylon.update_issueUpdate issue
- pylon.update_accountUpdate account
- pylon.upload_account_filesUpload account files
destructive
0Delete, cancel or archive. Ask first, or deny outright.
- No destructive actions.
Pylon in three steps.
- 01Your users connect PylonThey sign in to Pylon on Arc0 Connect, under your brand, and approve the access you ask for.
- 02You set the rulesReads run, and writes like “create issue” can wait for the user to approve.
- 03Any agent can actYour agent calls Pylon through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.
await arc0.policies.set('pylon', { read: 'allow', write: 'ask', // create_issue destructive: 'deny', }) # Claude Code: the same connection, one URL $ claude mcp add --transport http arc0 \ https://mcp.arc0.ai/u/u_8f2
How Pylon connects.
Pylon runs its own MCP server behind OAuth. Arc0 registers the client, users approve access on Arc0 Connect, and your agent reaches Pylon through the same endpoint, policies and audit log as every other app.
The same Pylon connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →
- AUTH
- OAuth 2.0 (MCP)
- CREDENTIALS
- Per-tenant encrypted vault
- MODEL SEES
- Results only, never credentials
- AUDIT LOG
- Every call, on every plan
Use Pylon from any agent.
Pylon and Arc0, answered.
Can I use Pylon with Claude, ChatGPT or Cursor?
Yes. Connect Pylon to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Pylon actions you allow.
How do users connect Pylon?
Pylon runs its own MCP server behind OAuth. Arc0 registers the client, users approve access on Arc0 Connect, and your agent reaches Pylon through the same endpoint, policies and audit log as every other app.
Which Pylon actions can my agent take?
12 in total: 8 read, 4 write and 0 destructive, such as “create issue”. Your policies decide which of them each agent may call.
Can I make my agent read-only in Pylon?
Yes. Allow read actions and deny writes in the Pylon policy. Your agent can still look things up, and any write it attempts is blocked and logged.
Can my own backend call Pylon too?
Yes. The same Pylon connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.
Plug Pylon into your agent.
Your users connect Pylon once, under your brand. Your agent gets 12 actions behind your policies, with every call on the record.
Free to build · MCP + REST · Audit log on every plan