Skip to content

Helpdesk

Pylon MCP connector

The Pylon connector lets Claude, ChatGPT, Cursor, and the Elaichi Agent read and update the accounts, contacts, teams, and account highlights in Pylon, with every action tied to the person who signed in and recorded in an audit log.

  • How it connects. Connects with an API key. The credential goes into a vault nobody reads back.

  • One address. https://api.elaichi.ai/mcp, the same for every user.

  • Their own access. An agent never gets more than the person it acts for.

How to connect

How to connect Pylon to Claude, ChatGPT or Cursor

Two steps, about a minute.

1

In Elaichi

Connect Pylon once

  1. Open Connections, choose Add connection, and pick Pylon.

  2. Optionally set Share with to give a team access, then press Connect.

  3. Paste a Pylon API key. One person generates a token in Pylon and pastes it once. Everyone else works through Share with, and never sees it.

The credential is vaulted. Nobody reads it back, not even the AI.

Add connection

Choose a connector.

pylon
Pylon
Acquire
Ada
Atomicwork
CM Mobile Service Cloud
Crisp
2

In your AI client

Point it at one endpoint

Everyone in the organization uses the same address, and each person only ever reaches what their own account allows.

Connect Pylon to Claude

  1. 1

    Open Customize, then Connectors.

  2. 2

    Press Add.

  3. 3

    Name it, paste the MCP server URL, then Continue.

    https://api.elaichi.ai/mcp
  4. 4

    Sign in and approve.

On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.

Connect Pylon to ChatGPT

  1. 1

    Open Plugins, then press the + button.

  2. 2

    Name it and paste the endpoint into Server URL.

    https://api.elaichi.ai/mcp
  3. 3

    Leave Authentication on OAuth, then tick the risk acknowledgement.

  4. 4

    Press Create, then sign in and approve.

Works on the web today. The plugin directory lives at chatgpt.com/plugins.

Connect Pylon to Cursor

  1. 1

    Open ~/.cursor/mcp.json.

  2. 2

    Add the endpoint under mcpServers.

    https://api.elaichi.ai/mcp
  3. 3

    Reload Cursor, then sign in and approve.

~/.cursor/mcp.json

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

Set up per machine, so repeat it on each computer you work from.

Connect Pylon to any MCP client

  1. 1

    Add the endpoint as a remote MCP server.

    https://api.elaichi.ai/mcp
  2. 2

    Sign in and approve.

{
  "mcpServers": {
    "elaichi": {
      "url": "https://api.elaichi.ai/mcp"
    }
  }
}

The Elaichi Agent already has these tools, with nothing to set up.

Use cases

What teams do with Pylon through Elaichi

Every one of these runs inside the access the person already has, and lands in the same audit log.

  • Support

    Look up an account before replying

    Ask for the account behind an incoming request and get its contacts, highlights, and recent activity in one answer, so the reply matches what the customer already told you.

  • Customer Success

    Log the call notes as account activity

    After a check-in, dictate what was discussed and have it saved as an activity on the Pylon account, with an attachment for the deck or notes if there is one.

  • Customer Success

    Keep account highlights current

    Add a highlight when a customer flags a risk or a win, update it when things change, and remove it once it no longer applies.

  • Sales

    Create the account on handoff

    When a deal closes, create the Pylon account and its contacts from the details you already have, so support sees the customer from day one.

  • Operations

    Fix contact details across accounts

    Find contacts with an old email or job title, update them in place, and confirm the custom fields are filled in the way your team expects.

  • Operations

    Set up teams and check who is on them

    List Pylon users and their roles, create a new team for a region or product line, and update team membership as people move around.

Try asking

  • “Which Pylon accounts opened the most issues this week?”
  • “List Pylon teams and the users on each one.”
  • “Summarize open Pylon issues for our top three accounts.”

See all 55 Pylon tools below

AI tools

Pylon tools for your AI agents

55 tools are ready to call through Elaichi's MCP endpoint the moment you connect Pylon, governed by the same roles, restrictions, and audit log as everything else in Elaichi.

See it in Elaichi

What connecting Pylon gets you

6 screens from the product, each doing one job for your Pylon account.

The agent

Ask about Pylon accounts, get real answers.

Type a question in plain language and read it off live Pylon records.

  • accounts
  • issues
  • users
  • teams

Ask Elaichi to work across your apps.

Which Pylon accounts opened the most issues this week?

List Pylon teams and the users on each one.

Summarize open Pylon issues for our top three accounts.

Also runs in Claude, ChatGPT or Cursor

MCP clients

One Pylon endpoint for every MCP client.

Claude, ChatGPT and Cursor connect over OAuth, no SDK and no shared API key.

ElaichiMCP clients
Claude ChatGPT Cursor

Copy the endpoint

https://api.elaichi.ai/mcp
Client Connected by Status Last used
Claude
E

Emma Laurent

• Connected 4 minutes ago
Cursor
S

Sofia Ricci

• Connected 2 hours ago
ChatGPT
C

Clara Nowak

• Connected Yesterday

Tool catalog

55 Pylon tools ready without custom code.

Accounts, users, teams, roles and attachments are covered by named tools and methods.

  • List all Pylon me
  • List all Pylon users
  • Get single Pylon user by ID
  • Update a Pylon user by ID
ElaichiTools
Tool Action Description
List all Pylon me List Get details of the current user
List all Pylon users List List users in Pylon. Returns user fields: avatar_url, email, emails, id, name, role_id, and status in the response.
Get single Pylon user by ID Get Get a user by its id in Pylon. Returns user fields: avatar_url, email, emails, id, name, role_id, and status in the response.
Update a Pylon user by ID Update Update a user in Pylon. Requires id. Returns avatar_url, email, emails, id, name, role_id, and status for the updated user in the response.
List all Pylon user roles List List all user roles in Pylon. Returns id, name, and slug fields for each user role in the response.

Toolboxes

Every team gets its own Pylon toolbox.

Curate one toolbox per team so support sees Pylon tools that fit its work.

  • Support
  • Customer success
  • Engineering
  • Operations
ElaichiToolboxes
Name Source template Tools Created

Support toolbox

Pylon · issues and accounts

Pylon starter 18 Mar 4, 2026

Customer success toolbox

Pylon · accounts and contacts

9 Mar 2, 2026

Engineering toolbox

Pylon · escalated issues and attachments

24 Feb 27, 2026

Operations toolbox

Pylon · teams, users and roles

Pylon starter 6 Feb 19, 2026

Sales toolbox

Pylon · account records and onboarding

31 Jan 30, 2026

Leadership toolbox

Pylon · issue volume by team

12 Jan 22, 2026

Shared connections

Teammates use Pylon without seeing a credential.

One person connects the Pylon account, then shares it with named teams and members.

  • Support EMEA
  • Support US
  • Customer success
  • Escalations
ElaichiConnections
Connection Scope Status Access
PY

Pylon (Support EMEA)

Connected by Emma Laurent

Personal • Active 1 team · 6 members
PY

Pylon (Support US)

Connected by James Whitfield

Organization • Active 3 teams · 24 members
PY

Pylon (Customer success)

Connected by Sofia Ricci

Organization • Active 2 teams · 11 members
PY

Pylon (Escalations)

Connected by Daniel Ortega

Personal • Needs re-auth 1 team · 3 members
PY

Pylon (Onboarding)

Connected by Clara Nowak

Personal • Active Not shared
PY

Pylon (Operations)

Connected by Michael Brennan

Personal • Active 2 teams · 9 members

Audit log

Answer who touched which Pylon account.

Every call lands append only with time, actor, action, type and Pylon resource.

  • When
  • Who
  • What happened
  • Type
ElaichiAudit log
When Who What happened Type

2 minutes ago

Mar 6, 2026, 3:10 PM

E

Emma Laurent

[email protected]

Restriction Created Access

8 minutes ago

Mar 6, 2026, 3:04 PM

J

James Whitfield

[email protected]

Restriction Updated Access

14 minutes ago

Mar 6, 2026, 2:58 PM

S

Sofia Ricci

[email protected]

Role Assigned Access

20 minutes ago

Mar 6, 2026, 2:52 PM

D

Daniel Ortega

[email protected]

Pylon Users Updated MCP

26 minutes ago

Mar 6, 2026, 2:46 PM

C

Clara Nowak

[email protected]

Pylon Accounts Created MCP

32 minutes ago

Mar 6, 2026, 2:40 PM

M

Michael Brennan

[email protected]

Pylon Accounts List Toolbox

Launching soon

From answering questions to doing the work

A person no longer has to ask. A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations and live dashboards are launching soon, on the Black plan.

Automations

A schedule fires and Pylon work finishes.

Six steps fetch Pylon issues, group them, draft a digest, then post on approval.

Pylon digest

Run 418 · started 2 minutes ago · on behalf of Emma Laurent

  1. Schedule

    Every weekday at 08:00

    0.2s
  2. Fetch accounts

    Pylon

    1.4s
  3. Group by owner

    Transform

    0.1s
  4. Draft the digest

    Agent step

    Ran with 4 tools, returned a structured summary

    6.2s
  5. Approve the digest

    Needs approval

    Assigned to Michael Brennan

    Approve
  6. Post the digest

    Pylon

    Queued

Collections and dashboards

Pylon health numbers arrive without being asked.

Four metrics, 14 days of issues created and a team breakdown, computed on schedule.

Pylon health

Refreshed 4 minutes ago · every 15 minutes · from the accounts collection

Live

Accounts

1,284 ↓ 12%

Issues

96 ↓ 8%

Needs attention

3 ↑ 2

Updated this week

412 ↑ 9%

Accounts created

Last 14 days

By team

Share of activity

Support EMEA 34%

Support US 27%

Customer success 21%

Escalations 18%

FAQ

Frequently asked questions

How do I connect Pylon to Claude?

In Elaichi, choose Pylon from the connector catalog and paste in an API key from your Pylon settings; there is no OAuth application to register and no client ID or secret to generate. Then in Claude, open Customize, then Connectors, then Add, and paste the endpoint https://api.elaichi.ai/mcp. Claude will ask you to sign in to Elaichi, and from then on Pylon is available in your conversations.

Does Pylon work with ChatGPT and Cursor as well as Claude?

Yes. Once Pylon is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, any other MCP client, and the Elaichi Agent. You connect Pylon once and every client picks it up.

What can an AI agent actually do with my Pylon data?

With Pylon connected, an agent can look up accounts and contacts, create new ones, update details like emails and custom fields, log account activity, and add, change, or remove account highlights. It can also list Pylon users, roles, and teams, and create or update teams. Because Pylon exposes a large set of actions, short concrete asks such as "add a highlight to the Acme account" work better than long instructions.

Does connecting Pylon give the AI access to everything in my workspace?

No. Every request to Pylon runs as the person who signed in, so the agent can only see the accounts, contacts, and teams that person can already see in Pylon. Elaichi can narrow that further with restrictions, but it can never widen it beyond what Pylon itself allows that person.

Can my team share one Pylon connection?

Yes. One person connects Pylon with an API key and shares the connection with a team in Elaichi, and nobody else ever handles the key. Each teammate still signs in to Elaichi as themselves, so the audit log names the actual person behind every change to a Pylon account or contact.

Can I stop an agent from deleting or changing things in Pylon?

Yes. Restrictions in Elaichi work per action, so you can allow reading Pylon accounts and contacts while blocking deleting an account or removing a highlight, for example. A blocked action is never shown to Claude, ChatGPT, or any other client at all, so no prompt can reach it.

What happens to a Pylon connection when someone leaves?

When a person is offboarded in Elaichi, their access to Pylon through every AI client ends at once. If they had shared a Pylon connection with a team, that connection keeps working for everyone else. If you want Pylon gone entirely, disconnecting it once in Elaichi removes it from Claude, ChatGPT, Cursor, and every other client together.

Put Pylon in front of your team

Fourteen days on Gold, no credit card. Connect it once and pick what each team can call.