Pylon logo

Connect Pylon to Town

Escalations caught early, briefs that know every ticket, and issues filed from your calls. One click through Pylon's official MCP server.

Connect Pylon

Free to start

Flip the dog Townie waving in a striped shirt

Flip scanned the open tickets and put the hot ones in your brief.

See it work: a routine built on your support queue

Catch the escalations before they boil over

Set it up once. The radar comes to you.

How to connect the Pylon MCP to Town

  1. Open Integrations in Town

    Go to Integrations in your Town workspace (free to create) and find Pylon.

  2. Authorize the connection

    Sign in to Pylon when prompted. Town connects through Pylon's official MCP server (mcp.usepylon.com), so there's nothing to install or configure.

  3. Put your queue to work

    Done — your Townie can search issues, brief you on any account, and file or update tickets with your approval.

Read the Pylon connection docs

Just ask your Townie

Pylon holds the tickets. Town keeps the follow-through moving in your briefs, inbox, and standups.

  • “What's open with Acme right now?”

    Issues, threads, and owners, in one answer.

  • “What are customers hitting most this month?”

    Analyzed across issues, written up in Town's editor.

  • “Send eng the top issues from this week.”

    Summarized from Pylon threads, delivered to Slack or email.

Pylon integration FAQ

The Pylon MCP is Pylon's hosted Model Context Protocol server at mcp.usepylon.com — the official integration surface Pylon maintains. MCP is the open standard that lets AI assistants securely work with data from apps — in this case your support issues, messages, accounts, and contacts. Town connects to it in one click; no API keys or local setup.

Town only reads Pylon data when you (or a routine you configured) ask for it, and actions run as you — limited to what your Pylon account can already see and do. Issue and account changes wait for your approval. Read more about how Town approaches security.

By default, no — new issues, updates, and account changes are held for your approval, so nothing lands in the queue your team runs on without you seeing it.

Support issues and their messages, plus accounts, contacts, and users — scoped to what your Pylon account can see. Under the hood these are Pylon's MCP tools: search and read issues and messages, look up accounts and contacts, create and update issues, and update account records. Connecting requires Pylon's MCP Access role (ask your admin).

You need a Pylon account with the MCP Access role, and a Town account — free to start. The Pylon connection works on every Town plan.

Pylon's AI helps inside the support queue. Town connects support to everything else — tickets show up in customer briefs, meetings become filed issues, and the whole company can ask what customers are hitting.

What is Pylon?

Pylon is the support platform built for B2B — issues, shared Slack channels, and accounts in one place, so support and success teams run every customer conversation from a single queue.

Pylon holds the tickets; Town keeps the follow-through moving. Connected, escalations find you early, briefs know every open issue, and what customers say in meetings gets filed where support lives.

Visit usepylon.com

Meet your

Bo the bear Townie

bo@town.com

today.