Connect Claude, ChatGPT or Cursor to LeadLex.
The LeadLex MCP server lets your AI assistant search your contacts, log a meeting, check your pipeline and draft a follow-up, inside your own workspace and with your permissions.
https://mcp.leadlex.com/mcpStreamable HTTP. Sign in with OAuth 2.1, or use a workspace API key for scripts.
Paste one URL, then approve the connection in LeadLex.
Claude
- In Claude Desktop or on claude.ai, open Settings, then Connectors.
- Choose Add custom connector and paste the endpoint.
- Sign in to LeadLex and approve the permissions.
- Try: “Search my contacts for Daniel.”
Claude Code:
claude mcp add --transport http leadlex https://mcp.leadlex.com/mcpChatGPT
- On ChatGPT Business, Enterprise or Edu, go to Plugins, select the plus button and choose Add custom MCP server.
- Paste the endpoint.
- Sign in to LeadLex and approve the permissions.
Cursor and other clients
- Add LeadLex to your client’s MCP config, for Cursor
~/.cursor/mcp.json:
{ "mcpServers": { "leadlex": { "url": "https://mcp.leadlex.com/mcp" } } }- Add LeadLex to your client’s MCP config, for Cursor
99 tools across your CRM, inbox, calendar and the IP registers.
Contacts, companies, deals, tasks, meetings, notes, lists, events, prospecting, campaigns, email drafts and IP profiles. A few prompts and the tools they use:
Just met Daniel Weber from Halvorsen Medtech. Interested in a portfolio review, follow up next week.
upsert_crm_bundle: contact, company, deal, note and follow-up task in one callWhat deals am I sleeping on?
report_stale_dealsWhen am I free for a 30 minute call this week?
find_free_slot, then create_meetingDid Anna Lindqvist reply to my proposal?
search_emailsFind heads of IP at medtech companies in Munich and save them to a list.
find_prospects, reveal_prospect_emails (uses credits), save_prospects
The full list, with inputs and examples, is in the tool reference.
The assistant works inside your permissions, not around them.
Your workspace, and only what you can see
The server scopes every query to your workspace. The assistant never chooses the tenant, and it sees the same records you see in LeadLex.
You sign in, you choose the permissions
OAuth 2.1 with PKCE. The consent screen shows who you are signing in as and what the assistant may do: read, write, or run Lexi tasks. A read-only connection gets no write tools.
Nothing goes out on its own
Email tools draft, they do not send. Sending a campaign needs an admin setting that is off by default plus an explicit confirmation, and deletes need an explicit confirmation too.
Every call is logged
Each tool call is recorded with the connection, the tool, the result and the time, so an admin can see what an assistant did.
More on hosting and data handling on the security page.
Before you connect. The short answers.
Yes. LeadLex exposes its data and actions as a Model Context Protocol server, so Claude (and any future MCP-aware client) can read and act on firm data under the same permissions the user has. Setup takes about 20 minutes.
Any client that supports remote MCP servers over Streamable HTTP. LeadLex shows setup steps for Claude, ChatGPT, Codex and Cursor in Settings, under API & Data.
No. Most clients sign you in with OAuth: you approve the connection in LeadLex and you are done. Workspace API keys (X-API-Key) are there for scripts and servers, and only admins can create them.
Not on its own. The email tools write drafts. Campaign sending is off until an admin turns it on, and even then each send needs an explicit confirmation.
All of them. Every workspace can connect an AI assistant over MCP.
Yes. Every OAuth connection and API key can make 60 tool calls a minute. Above that the server answers 429 with a Retry-After header. Need more? Write to support@leadlex.com.
On docs.leadlex.com, generated from the same manifest the server is tested against. 99 tools today, grouped by area.
Every tool, resource and prompt, documented.
Authentication, client setup, the full tool reference and worked examples.
Open docs.leadlex.com