Connect ChatGPT and other MCP clients to Crumblelead

Crumblelead speaks MCP (Model Context Protocol), an open standard that lets AI assistants securely read and update your data. That means you are not limited to one assistant. If ChatGPT or another tool supports MCP, you can connect it to your workspace the same way you would connect Claude.

For Claude specifically, see Connect Claude to Crumblelead with MCP. The steps below apply to ChatGPT and other MCP clients.

Find your workspace address

In the left sidebar, click MCP & API.
Choose Let AI do your admin to open the Connect an AI assistant page.
Pick ChatGPT. Your workspace address is in step 2, with a Copy address button.

Connect ChatGPT

ChatGPT adds tools like Crumblelead through Developer mode, available on chatgpt.com for Plus, Pro, Business, Enterprise and Edu plans. On Business and Enterprise, a workspace admin may need to allow it first. There is no key to create: you sign in with your normal Crumblelead login.

In ChatGPT, open Settings, then Security and login, and switch on Developer mode.
Go to Plugins and click +. Name it Crumblelead and paste your workspace address as the server URL. Choose OAuth if asked, then click Create.
A Crumblelead window opens. Sign in if asked, then click Authorize.
In a new chat, type @Crumblelead and pick it from the list, then ask "how many open jobs do I have?"

ChatGPT shows each Crumblelead action it takes and asks you to confirm before it changes anything.

Other MCP tools (Claude Code, Cursor and more)

On the Connect an AI assistant page, pick Other tools and use Create key. Name it after the tool and copy the key straight away (it is only shown once).
Copy the command or configuration snippet on the page. Your address and key are already filled in.
Add it to your tool, restart it and ask a test question.

If your tool supports signing in with OAuth, you can skip the key: add the address on its own and approve Crumblelead when the window opens.

What the connection can do

Whichever assistant you use, it works only in your current workspace and follows your permissions. Grouped by what they help you do, the available tools let an assistant:

Find and read records — search candidates, jobs and clients, open a full profile, list who is in each pipeline stage, see stage counts, and list your calendar events.
Add new records — create candidates, clients and jobs, including reading a CV or job description from a link and extracting the details.
Keep work moving — add a candidate to a job, move applications between pipeline stages, move a client to a different stage, add notes, and attach documents from a link.
Report on performance — anyone can see their own numbers; company-wide revenue, top clients and the consultant leaderboard are for managers and admins only.
Remove records — delete candidates or clients, remove a candidate from a job, or delete a job (jobs can be restored by an admin; deleted candidates and clients cannot).

Permissions, team boundaries and keys

One workspace at a time. The connection only sees the workspace you are currently in. It cannot reach another team's data. Switch workspaces in Crumblelead to point it somewhere else.
Your role still applies. The assistant can only do what you are allowed to do. Confidential jobs stay hidden unless you can already see them.
Revoking access. Go to MCP & API and open API keys & connected apps. Click Disconnect next to an assistant you signed in from, or the delete icon next to an access key. Access stops straight away.
Active subscription required. The connection is disabled if the workspace subscription is not active.

FAQs

Does every AI assistant work?
Any assistant that supports MCP can connect. If it lets you add a server by address and sign in, do that; otherwise use an access key.

I cannot find Connectors in ChatGPT.
ChatGPT renamed Connectors to Plugins in 2026, and adding your own tool now needs Developer mode. Turn it on under Settings, then Security and login, then create the plugin from Plugins.

Can two assistants be connected at once?
Yes. Each one you sign in from shows up separately under connected apps. For tools that use a key, create one key per tool so you can turn them off independently.

Will the assistant see other consultants' candidates?
It sees the same data you would see in the app, scoped to your workspace and your role.

How do I stop an assistant completely?
Disconnect it under API keys & connected apps, or delete its access key.