MCP Server
Connect an AI agent
Use the official LeadX plugin in ChatGPT, or connect Claude, Cursor, and other MCP clients to look up companies, contacts, emails, and UCC filings.
The LeadX MCP server lets an AI assistant call the LeadX API directly. Ask a question in plain language and the assistant runs the matching LeadX lookup and answers with live data — no code, and no copying API keys between tools.
Connect once with your LeadX login and the assistant keeps working with your account's permissions, credits, and rate limits.
In ChatGPT, install the official LeadX plugin. You no longer need to create a custom connector.
Server URL
For Claude, Cursor, and other MCP clients, use this server URL:
https://agents.leadx.com/mcpThat single URL is all most clients need. LeadX supports the MCP Streamable HTTP transport and OAuth 2.1 browser sign-in, so compatible clients discover the login flow automatically.
Connect your client
- Open the official LeadX plugin in ChatGPT.
- Select Install plugin if shown, then Connect when prompted.
- Sign in to your LeadX account and select Allow on the permissions screen.
- Start a chat, select LeadX with an
@mention, and ask for the data you need.
You do not need to enter a server URL or configure a custom connector.
If your ChatGPT workspace blocks installation, ask your workspace administrator to enable the LeadX plugin.
How sign-in works
Connecting uses your normal LeadX login. There is no API key to copy and no separate MCP password.
The client asks LeadX for authorization
Your assistant registers itself and opens the LeadX authorization page in your browser, using OAuth 2.1 Authorization Code with PKCE.
You sign in to LeadX
If you already have a LeadX session, it is reused. Otherwise you complete the normal LeadX login and the request resumes. Your LeadX password is never sent to the MCP server.
You approve the permissions
LeadX checks your account's live entitlements first, so the consent screen only ever offers data your account can already access.
The assistant receives a token
The access token is bound to the LeadX MCP server specifically and refreshes in the background, so you stay connected without signing in again.
Permissions
Each permission you approve maps to a LeadX product area:
| Scope | Grants access to |
|---|---|
mcp.tools | Base access to the LeadX tool set |
companies.read | Company search and firmographics |
contacts.read | Contact search |
email.find | Work email lookup |
mobile.find | Mobile number lookup |
ucc.read | UCC debtor and secured-party filings |
all_attributes.read | Combined company attribute lookups |
bbb.read | Better Business Bureau ratings and reviews |
google_reviews.read | Google review data |
A scope your account is not entitled to is rejected and never appears on the consent screen. If a tool later needs a permission you did not grant, LeadX returns an insufficient_scope challenge — reconnect and approve the additional permission along with the ones you already granted.
Example prompts
Once connected, ask for what you need in plain language:
- "What's the work email for Brett Warren at warrenbakerlaw.com?"
- "Pull every attribute you can find for easttnplasticsurgery.com."
- "Find construction companies in Texas with 10 to 250 employees."
- "Who are the owners and executives at acmeplumbing.com?"
- "Which businesses financed Caterpillar or John Deere equipment in the last 90 days?"
- "Show me the UCC filings where Wells Fargo is the secured party in North Dakota."
- "What's the BBB rating and accreditation status for Trio Capital?"
- "Summarize what customers say in the Google reviews for easttnplasticsurgery.com."
See MCP tools for the full list of what the assistant can call.
Credits, limits, and permissions
MCP tool calls are ordinary LeadX API calls. They use the same endpoint permissions, rate limits, and credit charges as your direct API integration, billed to the LeadX account you signed in with.
LeadX rechecks your entitlements on every request. Tools you are not entitled to never appear in the assistant's tool list, and access stops immediately if an entitlement is revoked.
Assistants can be eager. Ask for a specific number of results — "the top 10" — when you want to control how many records a search returns and how many credits it spends.
API key access
Clients that cannot complete a browser sign-in — shared machines, servers, and CI — can send a LeadX API key instead:
POST https://agents.leadx.com/mcp
X-API-Key: <your_api_key>Your API key is created and managed in the LeadX platform. See Authentication for details.
An OAuth access token issued for the MCP server is only valid at https://agents.leadx.com/mcp. Do not send it to api.leadx.com, and do not send your API key to the MCP server as a bearer token.
Troubleshooting
The client shows a 401 or asks me to sign in again
Your access token expired or was revoked. Reconnect from the client's plugin or connector settings to sign in again.
A tool I expected is missing
Tools are filtered by your live account entitlements. If a product is not enabled for your account, its tools do not appear. Contact your LeadX account team to add it, then reconnect.
I get an insufficient_scope error
The tool needs a permission you did not approve. Reconnect and approve the challenged permission along with the ones you already granted.
I want to disconnect
Disconnect LeadX in your client's plugin or connector settings. LeadX honors OAuth token revocation, and API keys stay managed in the LeadX platform.