Pylon MCP connector
The Pylon connector lets Claude, ChatGPT, Cursor, Microsoft Copilot, 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.
- Connects with an API key
- Free 14-day trial
- No credit card
Which Pylon accounts opened the most issues this week?
Working in Pylon with Elaichi
-
List all Pylon me
-
List all Pylon users
-
Get single Pylon user by ID
How to connect Pylon to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Pylon MCP connector for Claude
-
1
Open Customize, then Connectors.
-
2
Press Add.
-
3
Name it, paste the MCP server URL, then Continue.
https://api.elaichi.ai/mcp -
4
Sign in and approve.
On Team and Enterprise, an Owner adds it once. Everyone else turns it on for themselves.
Pylon MCP connector for Claude Code
-
1
In a terminal, run
claude mcp addwith the endpoint.https://api.elaichi.ai/mcp -
2
Start Claude Code and run
/mcp. -
3
Pick elaichi, then sign in and approve in the browser.
Terminal
$ claude mcp add --transport http elaichi --scope user https://api.elaichi.ai/mcp
Use --scope project instead to share it with the repository through .mcp.json.
Pylon MCP connector for ChatGPT
-
1
Open Plugins, then press the + button.
-
2
Name it and paste the endpoint into Server URL.
https://api.elaichi.ai/mcp -
3
Leave Authentication on OAuth, then tick the risk acknowledgement.
-
4
Press Create, then sign in and approve.
Works on the web. The plugin directory lives at chatgpt.com/plugins.
Pylon MCP connector for Cursor
-
1
Open
~/.cursor/mcp.json. -
2
Add the endpoint under
mcpServers.https://api.elaichi.ai/mcp -
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.
Pylon MCP connector for Microsoft Copilot
-
1
In Copilot Studio, open your agent, then Tools, Add a tool, New tool and Model Context Protocol.
-
2
Paste the endpoint into Server URL, choose OAuth 2.0, then Dynamic discovery, and press Create.
https://api.elaichi.ai/mcp -
3
Create a new connection, sign in and approve, then press Add to agent.
-
4
Under Channels, open Teams and Microsoft Copilot and make the agent available in Microsoft Copilot.
- Server URL
- https://api.elaichi.ai/mcp
- Authentication
- OAuth 2.0
- Type
- Dynamic discovery
Microsoft Copilot was called Microsoft 365 Copilot. Keep the tool on end-user credentials, so each person signs in as themselves.
Connect Pylon to any MCP client
-
1
Add the endpoint as a remote MCP server.
https://api.elaichi.ai/mcp -
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.
What teams do with Pylon through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Pylon is logged.
-
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.”
What connecting Pylon gets you
6 screens from Elaichi, each doing one job for your Pylon account.
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, Cursor or Microsoft Copilot
The agent
Ask about Pylon accounts, get real answers.
Type a question in plain language and read it off live Pylon records.
Copy the endpoint
AI apps
One Pylon endpoint for every MCP client.
Claude, ChatGPT, Cursor and Microsoft Copilot connect over OAuth, no SDK and no shared API key.
Tool catalog
55 Pylon tools ready without custom code.
Accounts, users, teams, roles and attachments are covered by named tools and methods.
Toolboxes
Every team gets its own Pylon toolbox.
Curate one toolbox per team so support sees Pylon tools that fit its work.
Shared connections
Teammates use Pylon without seeing a credential.
One person connects the Pylon account, then shares it with named teams and members.
Audit log
Answer who touched which Pylon account.
Every call lands append only with time, actor, action, type and Pylon resource.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Automations, collections and live dashboards come with the Black plan.
Pylon digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch accounts
Pylon
1.4s -
✓
Group by owner
Transform
0.1s -
✓
Draft the digest
Agent step
Ran with 4 tools, returned a structured summary
6.2s -
Approve the digest
Needs approval
Assigned to Jake Morgan
Approve Deny -
Post the digest
Pylon
Queued
Automations
A schedule fires and Pylon work finishes.
Six steps fetch Pylon issues, group them, draft a digest, then post on approval.
Pylon health
Refreshed 4 minutes ago · every 15 minutes · from the accounts collection
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%
Collections and dashboards
Pylon health numbers arrive without being asked.
Four metrics, 14 days of issues created and a team breakdown, computed on schedule.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Pylon
All three can connect Pylon to an AI assistant, and all three have admin controls. They differ in where access lives and how you pay.
| What to check | Elaichi | Zapier MCP | Composio |
|---|---|---|---|
| Where the AI connects |
One address for the whole organization.
https://api.elaichi.ai/mcp
|
A server per member, created at sign-in. | An MCP endpoint per team, or an SDK. |
| Control over Pylon tools | Allow or restrict single Pylon tools, per role or user. | App and action restrictions on the account. | Role permissions, down to the action. |
| Record of calls | One audit entry per Pylon call. | A History tab of tool calls. | A log of every tool call. |
| Single sign-on | SAML or OIDC, plus SCIM, on Gold. | SAML on Enterprise. | SAML and OIDC on Enterprise. |
| Price | Free for one person; $15 per user per month on Gold. | 2 tasks per successful call. | Billed per tool call. |
Sources: Zapier MCP docs, security, usage; Composio docs, gateway, enterprise, pricing. Checked September 2026.
Longer take: Zapier MCP alternative and when you don't need an MCP gateway.
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.
No tools match your search.
Questions, answered
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, Microsoft Copilot, 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 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 restricting deleting an account or removing a highlight, for example. A restricted action still appears in Elaichi's tool search, flagged as restricted, but Claude, ChatGPT, or any other client cannot run it, whatever the prompt says.
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, Microsoft Copilot, and every other client together.
Does the Pylon MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Pylon is reached over the same MCP endpoint every client uses, so anything that speaks MCP can call it — Gemini, Codex, Claude Code, Windsurf, Cline, Zed and OpenCode among them — alongside Claude, ChatGPT, Cursor, Microsoft Copilot, and the Elaichi Agent. The tools on offer and the access behind them are identical whichever client asks. Only the setup screen differs.
Is Elaichi an alternative to Zapier MCP for Pylon?
Yes. Both let Claude, ChatGPT or Cursor use Pylon. Zapier MCP fits a team that already automates in Zapier, since each person signs in and acts as themselves in that account. Elaichi fits when IT wants one address for the whole company, per-tool rules by role, and a record of every Pylon call.
How is Elaichi different from Composio for Pylon?
Composio gives AI agents tools and sign-in handling across 1,000+ apps, for developers building agents or people using an assistant, billed per tool call. Elaichi gives a company's own people governed access to Pylon: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Pylon in front of your team
14 days of Black, no credit card. Connect it once and pick what each team can call.
When the trial ends, nothing is deleted. You move to the free Personal plan, and connections, roles and the audit log stay where they are.
Add one link to your AI app
The same link for everyone on your team.
https://api.elaichi.ai/mcp
ChatGPT
Claude
Cursor
Microsoft Copilot