# Cognism MCP connector

The Cognism connector lets Claude, ChatGPT, Cursor, and the Elaichi Agent search Cognism contacts and accounts, reveal and enrich records, check credits and opt-outs, all inside each person's own Cognism access with every call logged.

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

## Facts

| | |
| --- | --- |
| Application | Cognism |
| Category | Sales Intelligence |
| AI tools | 25 |
| Authentication | Connects with an API key |
| Needs your own OAuth app | No |
| MCP endpoint | https://api.elaichi.ai/mcp |
| Works with | Claude, ChatGPT, Cursor, any MCP client, and the Elaichi Agent |
| Tools advertised by name | Yes |

## What you can ask once Cognism is connected

- Find contacts at mid-market fintech accounts in the UK.
- Enrich this account list with company size and industry.
- Which accounts match our target technology stack this week?

## Connect Cognism in Elaichi

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

1. Open Connections, choose Add connection, and pick Cognism.
2. Optionally set Share with, then press Connect.
3. Paste a Cognism API key. One person generates a token in Cognism 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 Cognism tools are exposed, rename them, or freeze arguments before anyone points a client at it.

## Connect Cognism to 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.

## Connect Cognism to 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 today. The plugin directory lives at chatgpt.com/plugins.

## Connect Cognism to 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.

## Connect Cognism 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

Only Read is granted by default, which is not enough to call a Cognism tool. 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. Grant Read and Run tools. Think hard before granting Delete, which reaches into connected apps and cannot be undone.

## What teams do with Cognism through Elaichi

### Build a prospect list before the outreach block

Sales development. Ask for finance directors at mid-sized manufacturers in Germany and get a Cognism contact list back, filtered by job function, seniority, company size, industry, and country, ready to reveal and work through.

### Find the right buyers at a target account

Sales. Before a discovery call, pull the contacts Cognism holds at the account, check who sits at the management level you sell to, and reveal the phone and email for the two people you actually need.

### Enrich a webinar list with company details

Marketing. Hand over the sign-ups from last week and have each contact and account enriched from Cognism with industry, headcount, region, and technologies used, so scoring and routing happen the same day.

### Check how many credits are left this month

Revenue operations. Ask what remains on the Cognism contact and account subscriptions before a big list build, so the team does not run dry halfway through a campaign.

### Confirm nobody on the list has opted out

Compliance. Paste in a set of emails and have each one checked against the Cognism opt-out register before any sequence starts, with the full opt-out list on hand for a periodic review.

### Size a territory before assigning it

Sales leadership. Search Cognism accounts by country, state, company type, and industry code to see how many target companies a new territory actually contains, then decide how to split it across the team.

## Frequently asked questions

### How do I connect Cognism to Claude?

Connect Cognism in Elaichi first, which means pasting your Cognism API key when asked. 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 https://api.elaichi.ai/mcp as the endpoint. Claude asks you to sign in to Elaichi and Cognism searches, reveals, and enrichment are available in the conversation.

### Does Cognism work with ChatGPT and Cursor as well as Claude?

Yes. Once Cognism 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 Cognism once and every client picks it up.

### What can an AI agent actually do with my Cognism data?

It can search Cognism for contacts and accounts using the same filters you use in the app, such as job function, seniority, industry, company size, region, country, and technologies, then reveal or enrich the records you choose. It can also check how many Cognism credits remain on your contact and account subscriptions and confirm whether an email address is on the opt-out list. It works from the live Cognism records, not a copy someone exported last quarter.

### Does connecting Cognism give the AI my whole subscription and every credit?

No. Every request runs under the Cognism access of the person who signed in, so the AI can only search, reveal, or enrich what that person's Cognism subscription already allows, and credits are spent from their entitlement. Elaichi can narrow that further, for example by blocking reveals for a team, but it can never grant more than the person already has in Cognism.

### Can my team share one Cognism connection?

Yes. One person connects Cognism in Elaichi and shares it with a team, and nobody else ever sees or handles the Cognism API key. Each teammate still signs in to Elaichi as themselves, so the audit log names the actual person who ran a Cognism search or revealed a contact, not a shared account.

### Can I stop an agent from spending Cognism credits or revealing contacts?

Yes. Restrictions in Elaichi apply per action, so you can allow Cognism searches and filter lookups while blocking the reveal and enrichment actions that consume credits. A blocked action is never shown to Claude, ChatGPT, or Cursor at all, so no prompt, however worded, can reach it.

### What happens to a Cognism connection when someone leaves?

Offboarding the person in Elaichi ends their access to Cognism through every client at once. If they connected a shared Cognism account, it keeps working for everyone else on the team. Disconnecting Cognism once in Elaichi removes it from Claude, ChatGPT, Cursor, and every other client together.

## All 25 Cognism tools

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

- **List all Cognism search contacts** (List). Search Cognism contacts by name, job title, location, phone/email quality, account attributes, seniority, skills, education, and event criteria. Returns: id, firstName, lastName, fullName, jobTitle, account. Each Array field supports up to 1000 search terms; results match all input criteria. Response fields depend on the subscribed Contact Entitlement.
- **List all Cognism search accounts** (List). Search Cognism accounts by names, domains, industries, technologies, revenue, size, location, and other criteria. Returns matching account records with preview flags indicating available data points (id, name, hasDomain, hasWebsite, hasRevenue, hasTechnologies, hasHeadcount, hasLinkedinUrl, hasSic, hasNaics). Results match all input criteria; each array field supports up to 1000 terms. Max 100…
- **Cognism contacts redeem** (Action). Redeem Cognism contacts by providing redeemIds obtained from Search or Enrich API responses. Returns: totalResults, results with full contact data including id, fullName, firstName, lastName, jobTitle, account, phone numbers, and entitlement-based fields. Required: redeemIds (up to 20 IDs per request).
- **Cognism contacts enrich** (Action). Enrich a Cognism contact by providing identifiers such as email, linkedinUrl, or a combination of firstName, lastName, and jobTitle with accountName or accountWebsite. Returns: matchScore, results with id, fullName, firstName, lastName, jobTitle, redeemId, and has* availability flags. Default minMatchScore is 30; scores below 27 indicate low quality matches.
- **Cognism accounts redeem** (Action). Redeem accounts by id in Cognism to retrieve their full field values, spending credits. Pass the id values returned by Search Accounts or Enrich Account. Returns: total and result, where each account carries id, name, domain, industries, description, founded, website, linkedinUrl, revenue, sizeFrom, sizeTo, technologies, type, naics, sic, phone numbers and locations, subject to your entitlement. Required: redeemIds.
- **Cognism accounts enrich** (Action). Enrich an account in Cognism by supplying identifying input, returning a scored preview match. Best matched on a unique identifier (website, domain or linkedinUrl); supplying more inputs improves the match. Returns: matchScore and results, where each record carries id, name and has* flags indicating which datapoints are available - redeem the account to retrieve the actual values. Default minMatchScore is 40; scores below 35 indicate a low-quality match.
- **Cognism entitlements get contact subscription** (Get). Get the subscribed Contact Entitlement details in Cognism. Returns: contact Entitlement.
- **Cognism entitlements get account subscription** (Get). Get the subscribed Account Entitlement details in Cognism. Returns: account Entitlement.
- **Cognism filters search technologies** (Search). Search Cognism's supported technology filters by keyword. Returns: results, lastReturnedKey. Leave the search parameter empty to list all technologies. Maximum indexSize is 10,000.
- **Cognism filters list management levels** (List). List all management level filter values in Cognism for use in contact searches. Returns: results.
- **Cognism filters list company sizes** (List). List all company size filter values in Cognism for use in account searches. Returns: results.
- **Cognism filters list industries** (List). List all industry filter values in Cognism for use in account searches. Returns: results.
- **Cognism filters list job functions** (List). List all job function filter values in Cognism for use in contact searches. Returns: results.
- **Cognism filters list regions** (List). List world region filter values available for Cognism search queries. Returns: results.
- **Cognism filters list countries** (List). List country filter values available for Cognism search queries. Returns: results.
- **Cognism filters list states** (List). List state filter values available for Cognism search queries. Returns: results.
- **Cognism filters list sic codes** (List). List SIC code filter values available for Cognism search queries. Returns: results.
- **Cognism filters list isic codes** (List). List ISIC code filter values available for Cognism search queries. Returns: results.
- **Cognism filters list naics codes** (List). List NAICS codes available as search filter values in Cognism. Returns: results.
- **Cognism filters list skills** (List). List skills available as search filter values in Cognism. Returns: results.
- **Cognism filters list company types** (List). List company types available as search filter values in Cognism. Returns: results.
- **Cognism filters list seniority** (List). List seniority levels available as search filter values in Cognism. Returns: results.
- **Cognism compliance list opt outs** (List). List all contacts that have opted out in Cognism. Returns a paginated list of opted-out contacts including pageKey for cursor-based pagination. Truto handles pagination automatically.
- **Cognism compliance get opt out by email** (Get). Check whether a contact has opted out in Cognism by email address. HTTP 200 indicates the contact has opted out; HTTP 404 indicates they have not. Returns an empty response body on success. Required: email.
- **Cognism compliance get opt out by ID** (Get). Check whether a contact has opted out in Cognism by opt-out ID. HTTP 200 indicates the contact has opted out; HTTP 404 indicates they have not. Returns an empty response body on success. Required: optout_id.