Kaspr MCP connector
The Kaspr connector brings LinkedIn profile enrichment, credit balances and rate limits into Claude, ChatGPT, Cursor, Microsoft Copilot and the Elaichi Agent, so each person can pull contact details inside their own Kaspr access.
- Connects with an API key
- Free 14-day trial
- No credit card
Enrich this LinkedIn profile and give me the work email and phone
Working in Kaspr with Elaichi
-
List all Kaspr credits
-
List all Kaspr me
-
List all Kaspr rate limits
How to connect Kaspr to Claude, ChatGPT, Cursor or Microsoft Copilot
Step by step, for each AI app
Kaspr 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.
Kaspr 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.
Kaspr 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.
Kaspr 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.
Kaspr 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 Kaspr 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 Kaspr through Elaichi
Ask in plain English. Each person’s AI can do only what they’re allowed to, and every action it takes in Kaspr is logged.
-
Sales
Get a prospect's number before the call
Paste a LinkedIn profile link and Kaspr returns the work email and phone number, ready to dial. No switching tabs or copying between windows.
-
Sales development
Enrich a list of LinkedIn profiles at once
Hand over a batch of LinkedIn profiles from a target account and get back emails and phone numbers for each one, laid out in a table for the sequence.
-
Marketing
Fill the gaps in an event list
Attendees often sign up with a LinkedIn profile and little else. Enrich those profiles with Kaspr so the follow-up campaign has a work email to send to.
-
Recruiting
Reach a candidate outside LinkedIn messages
Enrich a candidate's LinkedIn profile to get a direct email or phone number, then draft the outreach in the same conversation.
-
Revenue operations
Check Kaspr credits before a big run
Ask how many Kaspr credits remain and what the rate limits allow before kicking off a large enrichment, so nobody burns the month's balance by Tuesday.
-
Sales leadership
Confirm which Kaspr account is connected
See the account details behind the shared Kaspr connection, along with its current credits and limits, when planning the quarter's outbound push.
Try asking
- “Enrich this LinkedIn profile and give me the work email and phone”
- “How many Kaspr credits do we have left this month?”
- “Enrich these five LinkedIn profiles and put the results in a table”
What connecting Kaspr gets you
6 screens from Elaichi, each doing one job for your Kaspr account.
Ask Elaichi to work across your apps.
Enrich this LinkedIn profile and give me the work email and phone
How many Kaspr credits do we have left this month?
Enrich these five LinkedIn profiles and put the results in a table
Also runs in Claude, ChatGPT, Cursor or Microsoft Copilot
The agent
Ask for contact details in plain language.
Paste a LinkedIn profile and the Elaichi Agent returns email, phone and credits left.
Copy the endpoint
AI apps
Use Kaspr from Claude, ChatGPT and Cursor.
One governed endpoint, connected once over OAuth, no SDK and no shared API key.
Tool catalog
4 Kaspr tools, ready with no code.
Enrich LinkedIn profiles and check credits, rate limits and account details from one catalog.
Toolboxes
Every team gets its own Kaspr toolbox.
Sales enriches profiles while revenue operations watches credits, each scoped to its own work.
Shared connections
Share one Kaspr connection, never the key.
Teammates enrich profiles through a connection without ever seeing the Kaspr API key.
Audit log
Know who enriched which profile and when.
Every Kaspr call is logged with who, what happened, type and 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. Workflows, collections and live dashboards come with the Black plan.
Kaspr digest
Run 418 · started 2 minutes ago · on behalf of Emily Carter
-
✓
Schedule
Every weekday at 8:00 AM
0.2s -
✓
Fetch profiles
Kaspr
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
Kaspr
Queued
Workflows
A schedule starts Kaspr enrichment end to end.
New LinkedIn profiles are enriched, grouped and drafted into a digest a person approves.
Kaspr health
Refreshed 4 minutes ago · every 15 minutes · from the profiles collection
Profiles
1,284 ↓ 12%
Credits
96 ↓ 8%
Needs attention
3 ↑ 2
Updated this week
412 ↑ 9%
Profiles created
Last 14 days
By team
Share of activity
Sales EMEA 34%
Sales North America 27%
SDR team 21%
Marketing 18%
Collections and dashboards
Kaspr credits and enrichments, reported on a schedule.
Four metrics, 14 days of profiles enriched, broken down by team, with no model involved.
For IT and engineering
Elaichi vs Zapier MCP vs Composio for Kaspr
All three can connect Kaspr 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 Kaspr tools | Allow or restrict single Kaspr 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 Kaspr 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.
Kaspr tools for your AI agents
4 tools are ready to call through Elaichi's MCP endpoint the moment you connect Kaspr, 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 Kaspr to Claude?
Two steps. In Elaichi, add the Kaspr connector and paste in your Kaspr API key from your Kaspr account settings. There is no OAuth application to register and no client ID or secret to generate. Then in Claude go to Customize, then Connectors, then Add, and paste https://api.elaichi.ai/mcp.
Does Kaspr work with ChatGPT and Cursor as well as Claude?
Yes. Once Kaspr 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 Kaspr once and every client picks it up.
What can an AI agent actually do with my Kaspr data?
An agent can take a LinkedIn profile and ask Kaspr for the person's work email and phone number, for one profile or a list. It can also tell you how many Kaspr credits are left, what the rate limits are and which Kaspr account is connected. Short asks like "enrich this profile" work better than long paragraphs.
Does connecting Kaspr give the AI all of my Kaspr credits and account?
Access follows the person who signed in to Elaichi, and the Kaspr connection runs with the permissions of the Kaspr account whose API key was added. Elaichi can narrow what each role or person is allowed to do with Kaspr, such as checking credits but not enriching profiles. It never widens access beyond what the Kaspr account already has.
Can I stop an agent from spending Kaspr credits or enriching profiles?
Yes. Restrictions in Elaichi apply per action, set on a role or on one person, so you can restrict Kaspr profile enrichment for a role while leaving credit and rate limit checks open. A restricted action still shows up in Elaichi's tool search, flagged as restricted, but no client can run it against Kaspr, whatever the prompt says.
What happens to a Kaspr connection when someone leaves?
Offboarding a person in Elaichi ends their access to Kaspr through every client at once. A shared Kaspr connection keeps working for everyone else on the team. If you disconnect Kaspr once in Elaichi, it is removed from Claude, ChatGPT, Cursor, Microsoft Copilot and every other client at the same time.
Does the Kaspr MCP connector work with Gemini, Codex, Claude Code or other MCP clients?
Yes. Kaspr 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 Kaspr?
Yes. Both let Claude, ChatGPT or Cursor use Kaspr. 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 Kaspr call.
How is Elaichi different from Composio for Kaspr?
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 Kaspr: one address, restrictions per role or user, and $15 per user per month. Both have role permissions and a log of every call.
Put Kaspr 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