Connecting ContactLevel to Claude or Codex (MCP)
Connect ContactLevel to Claude or Codex and ask your assistant about your contacts, companies, audiences, website visits and LinkedIn analytics. With write access, it can also create audiences and run syncs for you.
The server URL for every client is:
https://a.contactlevel.com/mcp
Choose a permission level
The recommended way to connect is to sign in with your ContactLevel dashboard account. No API key needed. During sign-in you select an organization and choose a permission:
Read only (default): search and retrieve contacts, companies, audiences, website visits, LinkedIn analytics and credit balances.
Read & write: everything above, plus create audiences, run syncs, start exports and change audience membership. Adding contacts uses Audience credits.
Claude (web or desktop)
In Claude, go to Settings → Connectors.
Click Add custom connector.
Name it ContactLevel and paste the server URL.
Leave the OAuth client ID and secret empty, then click Add.
Click Connect, sign in to ContactLevel and approve access.
Turn on the ContactLevel tools in your chat.
Claude Code
Add the server:
claude mcp add --transport http --scope user contactlevel https://a.contactlevel.com/mcp
Then sign in:
claude mcp login contactlevel
You can also run /mcp inside Claude Code, pick contactlevel and choose Authenticate.
Codex
Add the server:
codex mcp add contactlevel --url https://a.contactlevel.com/mcp
Then sign in:
codex mcp login contactlevel
Confirm it's listed:
codex mcp list
Check the connection
Ask your assistant to run getOrganizationId. It returns the organization name, ID and the permission level of the connection.
Using an API key instead
Command-line clients can send an X-Api-Key header with a key from Settings → Developers instead of signing in. API key connections are always read & write.
Good to know
Each connection covers one organization and one permission level. To work with several organizations, add a separate, clearly named connection for each.
A read-only connection gets a
403 insufficient_permissionerror when it tries an action. Reconnect with Read & write if you need actions.If a write action times out, check whether it went through before you retry.
Deleting the MCP-KEY in Settings → Developers breaks every connection that uses it.