# 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.

Source: https://elaichi.ai/connectors/kaspr/

## Facts

| | |
| --- | --- |
| Application | Kaspr |
| Category | Sales Intelligence |
| AI tools | 4 |
| Authentication | Connects with an API key |
| Bring your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, Microsoft Copilot, any MCP client, and the Elaichi Agent |
| Tools advertised by name | No. Connected tools are never listed one by one, however few there are. The endpoint advertises `search_tools` and `execute_tool` instead |

## What you can ask once Kaspr is connected

- 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

## Connect Kaspr in Elaichi

This happens once for the organization, before any client is involved.

1. Open Connections, choose Add connection, and pick Kaspr.
2. Optionally set Share with, then press Connect.
3. Paste a Kaspr API key. One person generates a token in Kaspr and pastes it once. Everyone else works through Share with, and never sees it.

Credentials are vaulted and nobody, including the AI, reads them back. The connection becomes a toolbox immediately, so you can curate which Kaspr tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Kaspr MCP connector for Claude

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

1. Open Customize, then Connectors.
2. Press Add.
3. Name it, paste the MCP server URL, then Continue.
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

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

1. In a terminal, run `claude mcp add` with the endpoint.
2. Start Claude Code and run `/mcp`.
3. Pick elaichi, then sign in and approve in the browser.

```bash
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

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

1. Open Plugins, then press the + button.
2. Name it and paste the endpoint into Server URL.
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

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

1. Open `~/.cursor/mcp.json`.
2. Add the endpoint under `mcpServers`.
3. Reload Cursor, then sign in and approve.

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

## Kaspr MCP connector for Microsoft Copilot

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

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.
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.

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

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

1. Add the endpoint as a remote MCP server.
2. Sign in and approve.

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

## What the consent screen decides

Every scope the client asks for starts ticked except "Delete things", which you tick yourself. Calling a Kaspr tool needs "Use your connected apps". Over MCP there is no trusted place to confirm a write in the moment, so the consent screen is the standing approval rather than a formality. Think hard before granting Use your connected apps, which can also delete in connected apps and cannot be undone.

## What teams do with Kaspr through Elaichi

### Get a prospect's number before the call

Sales. Paste a LinkedIn profile link and Kaspr returns the work email and phone number, ready to dial. No switching tabs or copying between windows.

### Enrich a list of LinkedIn profiles at once

Sales development. 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.

### Fill the gaps in an event list

Marketing. 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.

### Reach a candidate outside LinkedIn messages

Recruiting. Enrich a candidate's LinkedIn profile to get a direct email or phone number, then draft the outreach in the same conversation.

### Check Kaspr credits before a big run

Revenue operations. 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.

### Confirm which Kaspr account is connected

Sales leadership. See the account details behind the shared Kaspr connection, along with its current credits and limits, when planning the quarter's outbound push.

## 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. Endpoint: 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](https://docs.zapier.com/mcp/get-started/quickstart), [security](https://docs.zapier.com/mcp/manage/security), [usage](https://docs.zapier.com/mcp/features/usage); Composio [docs](https://docs.composio.dev/docs/composio-connect), [gateway](https://composio.dev/mcp-gateway), [enterprise](https://composio.dev/enterprise), [pricing](https://composio.dev/pricing). Checked September 2026.

Longer take: [Zapier MCP alternative](/blog/zapier-mcp-alternative/) and [when you don't need an MCP gateway](/blog/when-you-dont-need-an-mcp-gateway/).

## Frequently asked questions

### 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 my team share one Kaspr connection?

Yes. One person connects Kaspr in Elaichi and shares the connection with a team, and nobody else ever handles the Kaspr API key. Each teammate still signs in to Elaichi as themselves, so the audit log names the person who ran each Kaspr enrichment.

### 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.

## All 4 Kaspr tools

Every tool below is callable through https://api.elaichi.ai/mcp once Kaspr is connected, subject to the toolbox it is in and the restrictions on the caller.

- **List all Kaspr credits** (List). Get the remaining credits in the Kaspr workspace. A workEmailCredits value of -1 means unlimited. Returns: workEmailCredits, directEmailCredits, phoneCredits, exportCredits.
- **Kaspr linkedin profiles enrich** (Action). Retrieve a prospect's work email, direct (personal) email and phone number from Kaspr using their LinkedIn profile. Returns the enriched profile: id, name, professionalEmails, personalEmails, phones, title, company, fetchedAt, processingTime. Requested data types consume credits, plus one export credit per successful call. Required: id, name.
- **List all Kaspr me** (List). Verify that the connected Kaspr API key is valid. Returns: user (identifies the key owner; Kaspr shows an email address here).
- **List all Kaspr rate limits** (List). Get the request rate limits configured for the Kaspr workspace. Returns: dailyLimit, hourlyLimit, minutelyLimit.
