Skip to main content
The LeadLex MCP server lets an AI assistant work inside your LeadLex workspace. You ask in plain language. The assistant searches your contacts, creates a deal, books a follow-up task or drafts a campaign, and it does so with your own CRM data. MCP (Model Context Protocol) is the open standard that AI assistants use to talk to outside tools. LeadLex runs a remote MCP server, so there is nothing to install.

​
Endpoint

The server speaks streamable HTTP. You can sign in with OAuth 2.1 or with a workspace API key. See Authentication.

​
What the server exposes

99 tools

Contacts, companies, deals, tasks, meetings, notes, email, campaigns, prospecting, reports and more.

5 resources

Read-only records the assistant can load on demand, such as a workspace snapshot.

6 prompts

Ready-made workflows such as a weekly pipeline review.

​
Connect your assistant

Claude

Claude.ai, Claude Desktop and Claude Code.

ChatGPT

Add LeadLex as a custom connector.

Cursor

Add LeadLex to your Cursor MCP config.

Other clients

Any client that supports remote streamable HTTP servers.

​
How it relates to the REST API

The MCP server and the REST API work on the same workspace data. Use MCP when an AI assistant is the user. Use the REST API when your own code is the client.

​
Workspace isolation

Every call runs inside the workspace of the account that signed in. You never pass a workspace or company id, and the tools do not accept one. Read more on the Security page.

​
Availability

MCP is included on every LeadLex plan. OAuth connections can make 60 tool calls a minute; above that the server answers 429 with a Retry-After header.