Want to ask ChatGPT or Claude about your LeadSimple contacts, leads, processes, or tasks? LeadSimple’s MCP connection lets your AI app look up information you’re allowed to see and, if you choose, make a few basic changes.
What is MCP?
MCP stands for Model Context Protocol. Think of it as a standard connection that lets an AI assistant work with another app. You ask a question in everyday language, the assistant requests the relevant information from LeadSimple, and it uses the results to answer you.
For example, you could ask, “Find the process for 123 Main Street and show me its next task.” The assistant can look up the record instead of asking you to copy and paste it into the chat.
LeadSimple hosts this connection online as part of its existing application. There’s no software to install on your computer and no code to write. Connecting gives the assistant a specific set of actions it can use; your LeadSimple permissions still apply.
Before you connect
You need an active LeadSimple login and access to the records and products you want to use.
Your ChatGPT or Claude account must allow custom connections. Your AI workspace may require an administrator to enable them.
Use the custom setup below while LeadSimple’s public directory listings are pending.
LeadSimple MCP server address: https://api.leadsimple.com/mcp
You sign in through LeadSimple using your usual login and multifactor authentication, if required. You don’t need a LeadSimple API key. Enter your password only on the LeadSimple sign-in page, never in the chat or a connector configuration field.
Connect in ChatGPT
On the web, open ChatGPT’s Plugins page.
Use the plus button and choose Add custom MCP server.
Name it LeadSimple and enter the server address above.
Choose OAuth authentication. If asked how ChatGPT identifies itself, select CIMD (its published client identity). Leave manually supplied client credentials blank.
Read the connection warning, acknowledge it if you want to proceed, and choose Create as a plugin.
Open the new plugin in your personal plugins and install it. Follow any connection or sign-in prompts.
On LeadSimple’s approval page, check the displayed account and user, choose the access you want to grant, and approve the connection.
Start a Work chat, type @, and select LeadSimple. Try: “Which LeadSimple account am I connected to, and what can you access?”
Menu names and availability can vary by account or workspace. These steps follow OpenAI’s custom MCP connection guide and its plugin setup guide.
Connect in Claude
Open Customize → Connectors in Claude.
Choose + Add, then Add custom connector.
Name it LeadSimple, paste the server address above, and continue.
Review the detected authentication. Choose to sign in now and use Claude’s published identity, if prompted. LeadSimple uses account sign-in; no API key or custom request headers are needed.
Finish adding the connector and follow the LeadSimple sign-in and permission prompts.
Enable LeadSimple for the conversation from the chat’s plus menu under connectors.
On a Team or Enterprise workspace, an authorized workspace administrator first adds the web connector in the organization’s connector settings. Each member then connects using their own LeadSimple login. See Claude’s custom connector guide for account-specific steps.
Choose what the assistant can access
The LeadSimple approval page lets you choose categories of information. “Read” access lets the assistant look up information. “Write” access lets it create or edit the supported records.
Optional write permissions start unchecked. Leave them unchecked if you only want help finding and summarizing information. Some connection requests may offer only read access.
The assistant’s access depends on all of the following: what you approved, your current LeadSimple plan and products, your user permissions, and which records you can see. Approving a category does not unlock a product or grant access to a restricted record.
What can it help with?
Contacts: Find someone by name, company, email, or phone, and read their contact details.
Properties: Find a property by name or address and read its details.
Processes and workflows: Find processes, review their stage, owner, due date, overdue status, related contacts and properties, and next available task. It can also read workflow stages and configured steps. Requires the Processes product and appropriate access.
Pipelines and leads: Find pipelines and leads, review stages and lead counts, and see a lead’s owner and next task. Counts include only leads you can access. Requires the Pipelines product and appropriate access.
Tasks: List available tasks, including tasks linked to a lead or process, and read instructions and missing information required for completion. Requires the Tasks product and appropriate access.
Notes: Read notes attached directly to an accessible contact, property, or process. Notes intended for a different audience are excluded.
Your connection: Check the connected account, approved permissions, read-only status, and Social Security number filtering setting.
Currently unavailable: Reading or searching emails, text messages, and call transcripts is temporarily disabled. There is no setting you can turn on to restore this access.
What changes can it make?
With the matching optional write permission, the assistant can:
Create a contact with a name or company, plus one email address and one phone number. Existing contacts can have their names or company edited; email and phone edits are not supported.
Create a lead assigned to you, linked to an existing accessible contact, in an active stage of an accessible, unprotected pipeline. Existing leads can have their name or comments edited.
Create a manual to-do assigned to you, either on its own or attached to an accessible lead or process.
Creating a lead through MCP does not start its workflow, send notifications, or set up a tracking phone number. Editing a lead does not restart its workflow. Contact edits still follow LeadSimple’s normal sync behavior, so connected accounting systems may receive those changes.
The connection tells the assistant to confirm changes with you. Review the proposed record and details before approving. LeadSimple also protects supported retries from creating duplicate records and rejects edits if a record has changed since the assistant last read it.
What can’t it do?
The current connection cannot send messages, complete tasks, move leads between stages, delete records, or change billing, permissions, or credentials. It also does not provide dedicated tools for units, leases, work orders, users, or custom fields.
Try these questions
“Use LeadSimple to find Jane Smith and show her contact details.”
“Show my open tasks and include links to the LeadSimple records.”
“Find the process for 123 Main Street. What stage is it in, who owns it, and what’s the next task?”
“Summarize the notes attached to this property.”
“Create a manual task for me to follow up tomorrow. Show me the details before saving.” Requires task write permission.
Results may arrive in batches or include only part of a long record. Ask the assistant to check for more results, and review the linked LeadSimple records when completeness matters. An overdue process is not necessarily blocked, and a missing next task does not prove a process is complete.
Manage permissions or disconnect
In LeadSimple, go to Settings → Integrations → AI apps (MCP). You can review connections and their last-use time, remove permissions, save your changes, or disconnect an app. Granting additional access requires a new connection approval that requests those permissions.
LeadSimple administrators can review team connections and disconnect them. Only the member who connected an app can change that connection’s permissions. Access is checked each time the assistant makes a request, so changes to your LeadSimple access also affect future requests.
Disconnecting stops future access. It does not remove information the AI app has already received; that information remains subject to the AI provider’s data policies.
How does Social Security number filtering work?
The optional Mask detected Social Security numbers setting is off by default. It attempts to hide detected SSNs in notes shared through the connection. It does not filter contact fields, task instructions, or workflow step instructions. Detection is best effort: if filtering fails, the original response is delivered. Do not treat it as a guarantee that sensitive information will be removed.
Having trouble?
Can’t add a custom connection? Check your AI account’s options and ask your workspace administrator about restrictions.
Don’t see AI apps (MCP) in LeadSimple? The settings page may not be enabled for your account. Contact LeadSimple support.
A record or action is missing? Check your selected permissions, product access, and whether you can access that record in LeadSimple itself.
A change was refused because the record changed? Ask the assistant to read it again and show you the updated details before retrying.
The connection stopped working? Reconnect and sign in again. If the problem continues, contact support.
Need help? Visit the LeadSimple Help Center or contact LeadSimple support.