Leap MCP connector
The Leap connector gives Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent governed access to Leap customers, appointments, jobs, estimates and contracts, with every call running as the signed-in person and logged.
- Connects with an API key
- Free 14-day trial
- No credit card
Show me tomorrow's appointments for the roofing division
Working in Leap with Elaichi
-
List all Leap appointment result options
-
List all Leap appointment results
-
List all Leap appointments
How to connect Leap to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Leap 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.
Leap 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.
Leap 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.
Leap 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.
Leap 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 Leap 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 Leap through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Leap is logged.
-
Sales
Catch the customer up after a visit
Back in the truck, tell the agent how the appointment went and it records the appointment result and updates the Leap customer with what changed.
-
Sales
Book the next appointment without opening Leap
Ask for a follow-up on Thursday afternoon with the right division and the agent creates the Leap appointment against the customer.
-
Office
Find a homeowner and everyone attached to them
Ask for a customer by name and get their Leap record, their contacts and their recent appointments in one answer, no clicking through screens.
-
Production
Attach the signed contract to the job
Hand the agent the signed contract or the final estimate and it uploads it to the Leap job so the crew sees the right paperwork.
-
Finance
Check the job numbers before invoicing
Pull the Leap job financial summary and any change orders for a job, then ask what moved since the original estimate.
-
Estimating
Keep the price list current
Create new line items, update prices on existing Leap items and retire the ones you no longer sell, all from a short request.
Try asking
- “Show me tomorrow's appointments for the roofing division”
- “Update the Smith customer's address and phone number”
- “What's the financial summary on the Johnson job?”
What connecting Leap gets you
6 screens from Elaichi, each doing one job for your Leap account.
Ask Elaichi to work across your apps.
Show me tomorrow's appointments for the roofing division
Update the Smith customer's address and phone number
What's the financial summary on the Johnson job?
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask about Leap customers in plain language.
Type a question and the Elaichi Agent answers from live Leap appointments, customers and jobs.
Copy the endpoint
AI apps
Use Leap from Claude, ChatGPT and Cursor.
One governed endpoint, signed in as yourself, with no SDK and no shared API key.
Tool catalog
60 Leap tools, ready with no code.
Customers, appointments, items, change orders and job financials, covered without writing a connector.
Toolboxes
Every team gets its own Leap toolbox.
Sales, production and finance each see the Leap tools their work calls for.
Shared connections
Share a Leap connection, not the API key.
One person connects Leap once and teammates work through it without seeing a credential.
Audit log
Know who changed which Leap customer.
Every call is logged with who, when, what happened and which Leap record it touched.
From answering questions to doing the work
A trigger starts the work, inside the same permissions and the same audit log as everything else. Workflows, collections and live dashboards come with the Black plan.
Leap digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch customers
Leap
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
Leap
Queued
Workflows
A schedule drafts your Leap appointment digest.
A trigger fetches Leap appointments, groups them, drafts a digest, and a person approves it.
Leap health
Refreshed 4 minutes ago · every 15 minutes · from the customers collection
Customers
1,284 ↓ 12%
Appointments
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Customers created
Last 14 days
By team
Share of activity
Sales North 34%
Sales South 27%
Office 21%
Production 18%
Collections and dashboards
Leap job health, computed without a model.
Four metrics, 14 days of customers created and a team breakdown, refreshed on a schedule.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Leap
All three can connect Leap 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 Leap tools | Allow or restrict single Leap 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 Leap 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.
Leap tools for your AI agents
60 tools are ready to call through Elaichi's MCP endpoint the moment you connect Leap, 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 Leap to Claude?
Two steps. In Elaichi, add Leap and paste in your Leap API key, which is the only sign-in step, with no OAuth application to register and no client ID or secret to generate. Then in Claude open Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp. Claude signs you into Elaichi and Leap is ready to use.
Does Leap work with ChatGPT and Cursor as well as Claude?
Yes. Once Leap is connected in Elaichi, the same endpoint, https://api.elaichi.ai/mcp, works in Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client and the Elaichi Agent. You connect Leap once and every client picks it up.
What can an AI agent actually do with my Leap data?
It can look up Leap customers and their contacts, create and update customers, book and update appointments, record appointment results, manage items and item categories, upload contracts and estimates to jobs, and pull job financial summaries and change orders. Short, concrete asks work best, such as "book an appointment for the Garcias next Tuesday at 2" rather than a long paragraph.
Does connecting Leap give the AI access to every customer and job?
No. Every call into Leap runs as the person who signed in, so the agent sees only the Leap customers, appointments and jobs that person could already open. Elaichi can narrow that further with restrictions, and it never widens what Leap itself allows.
Can I stop an agent from deleting or changing things in Leap?
Yes. Restrictions in Elaichi apply per action, so you can allow reading Leap customers while restricting updates, or restrict deleting items entirely, for a role or for one person. A restricted action still shows up in Elaichi's tool search, flagged as restricted, but no client can run it no matter what the prompt says.
What happens to a Leap connection when someone leaves?
Offboard them in Elaichi and their access to Leap through every client ends at once. A shared Leap connection keeps working for everyone else on the team. If you want to remove Leap altogether, disconnect it once in Elaichi and it disappears from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client.
Does the Leap MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Leap 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 Leap?
Yes. Both let Claude, ChatGPT or Cursor use Leap. 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 Leap call.
How is Elaichi different from Composio for Leap?
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 Leap: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Leap 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