Admin setup
For workspace and organization admins. This page walks you through adding the Leadbay connector once, for your whole organization, so every member can connect without needing admin rights themselves.
If you landed here because a teammate asked you to "add the Leadbay connector" — you're in the right place. It takes a couple of minutes, there are no API tokens to hand out, and each member still signs in with their own Leadbay account.
Are you sure you need this? Only organization plans gate custom connectors behind an admin:
Claude — Team and Enterprise workspaces.
ChatGPT — Business and Enterprise workspaces.
On an individual paid plan (Claude Pro/Max, ChatGPT Plus/Pro), there's no admin step — you can add the connector yourself. Just follow the Quickstart or Installation guide.
Claude (Team & Enterprise)
As a primary owner or admin, you add Leadbay as an organization custom connector. Once it's added, it appears in every member's connector directory and they connect to it individually.
1. Open the Add custom connector form. Use this link (or in Claude, go to Settings → Connectors, then the + next to the search bar → Add custom connector):
2. Add it for the organization. Fill in the fields, and if Claude offers a choice of scope (organization vs. just you), choose the organization scope so every member gets it:
Name:
LeadbayURL:
https://mcp.leadbay.app/mcp
Leave the Advanced settings as they are — Individual sign-in is what you want. Each member authenticates with their own Leadbay login; you are not sharing one account across the team.
3. Click Add. That's the admin part done — Leadbay now shows up in your members' connector directory.
Members can't add it themselves. In a Team or Enterprise workspace, members don't have the Add custom connector option — that's exactly why this admin step exists.
What your members do next
Once you've added the connector, send your team these three steps (no admin rights needed — each person signs in with their own Leadbay account):
1. Find the Leadbay connector. In Claude, open Settings → Connectors and search "Leadbay" — it appears under Custom connectors. Open it.
2. Click Connect and sign in. A Sign in with Leadbay page opens in the browser — log in and click Approve. The tab closes and the connector shows as connected.
3. Ask for leads. Open a new chat and try "Show me today's leads." Claude replies with a ranked shortlist — that means it's fully connected. 🎉
The full member walkthrough (with the first-message tips) lives in the Quickstart.
ChatGPT (Business & Enterprise)
On Business and Enterprise workspaces, custom MCP connectors are off until a workspace owner or admin allows them. You don't add Leadbay for everyone here — you unlock the ability, and each member then adds it themselves.
Open your workspace settings (workspace menu, bottom-left → Settings).
Under the connector / apps controls, allow custom connectors for the workspace (this is the workspace-level switch that gates Developer-mode custom apps for members).
Let your members know they can now add Leadbay.
What your members do next
Unlike Claude, ChatGPT members add the app themselves once you've allowed custom connectors. Send them the ChatGPT section of the Installation guide — each member:
Turns on Developer mode (Settings → Apps → Advanced settings).
Clicks Create app and fills in Name
Leadbay MCP, Server URLhttps://mcp.leadbay.app/mcp, and Authentication: OAuth.Clicks Sign in with Leadbay MCP and logs in with their own Leadbay account.
Enables the Leadbay MCP app from the composer + / tools menu, then asks for leads.
The exact wording and location of the "allow custom connectors" control changes as ChatGPT's admin console evolves. If you can't find it, search the workspace settings for connectors or apps, or check OpenAI's current admin documentation.
Claude Code and Codex need no admin step — they're per-user CLI clients with no organization gate. Each member just runs the one-line add command from the Installation guide on their own machine.
Where to next
InstallationQuickstartLast updated