docs(mcp): add admin setup page for org installation#15
Merged
ArtyETH06 merged 8 commits intoJul 2, 2026
Merged
Conversation
Org members (Claude Team/Enterprise, ChatGPT Business/Enterprise) can't add the Leadbay custom connector themselves — an admin must add/allow it first. The install docs only had a one-line inline hint and no page walking an admin through the org-wide setup. Add leadbay-mcp/admin-setup.md (Claude + ChatGPT admin flows, plus a "no admin step" note for the CLI clients) and repoint the existing "not an admin?" hints in quickstart.md and installation.md at it. Wire the page into SUMMARY.md after Installation. Co-Authored-By: Claude <noreply@anthropic.com>
For people who can't get the custom-connector / MCP-URL route to work (option missing, admin can't add it), document the Claude Desktop .dxt extension as a per-user, no-admin escape hatch — double-click install, same one-tap Sign in with Leadbay. Canonical download URL (github.com/leadbay/mcp/releases/latest/download/leadbay-latest.dxt). Cross-link it from the installation troubleshooting row. Co-Authored-By: Claude <noreply@anthropic.com>
There's a single main server URL (https://mcp.leadbay.app/mcp); the /fr/mcp "EU instance" split no longer applies. Remove the US-vs-EU hints from quickstart, installation, and admin-setup, and the two EU-referencing troubleshooting rows in installation. Co-Authored-By: Claude <noreply@anthropic.com>
The admin setup page had per-user member content that isn't an admin action — the Claude Code/Codex install commands and the .dxt extension fallback. Remove both from admin-setup (leaving a one-line note that the CLI clients have no admin step). Move the .dxt fallback into the Claude Desktop section of the installation page, where the per-user install steps live, and repoint the troubleshooting row there. Co-Authored-By: Claude <noreply@anthropic.com>
The admin page explained how an admin adds/allows the connector but only gestured at what members do afterward. Add explicit "What your members do next" steps to both sections: for Claude, find the connector in the directory → Connect → sign in → ask for leads (with the existing directory/connect screenshots); for ChatGPT, the per-member Create app + OAuth flow. Co-Authored-By: Claude <noreply@anthropic.com>
The quickstart non-admin hint only told members to ask their admin. Add the self-serve option: on Claude Desktop a non-admin can skip the connector and install the .dxt extension themselves — no waiting on an admin. Links to the .dxt fallback in the installation guide. Co-Authored-By: Claude <noreply@anthropic.com>
The quickstart and installation troubleshooting links landed on the Claude Desktop section, not the .dxt fallback itself. Repoint both at the precise anchor (#fallback-install-the-.dxt-extension), verified against the rendered GitBook HTML, so the link jumps straight to the fallback steps. Co-Authored-By: Claude <noreply@anthropic.com>
A heading slug containing a literal "." (fallback-install-the-.dxt- extension) doesn't reliably resolve as a URL fragment — the link loaded the page but didn't scroll to the section. Rename the heading to "Fallback: install the extension" (clean slug, body still says .dxt) and repoint both deep links at #fallback-install-the-extension. Co-Authored-By: Claude <noreply@anthropic.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What
Adds a dedicated Admin setup page to the Leadbay MCP docs and points the existing "not an admin?" install hints at it.
Why
Org members (Claude Team/Enterprise, ChatGPT Business/Enterprise) can't add the Leadbay custom connector themselves — a workspace admin must add or allow it first. The install docs only carried a one-line inline hint and linked back to the end-user Installation page; there was no page walking an admin through the org-wide setup, and no documented fallback when the connector route is blocked.
Changes
leadbay-mcp/admin-setup.md:.dxtextension fallback — for anyone who can't get the connector/MCP-URL route to work, the Claude Desktop.dxtextension is a per-user double-click install with no org connector gate. Uses the canonicalleadbay/mcprelease download URL.quickstart.mdandinstallation.md(and the "custom connector option missing" troubleshooting row, which also links the.dxtfallback) at the new page.SUMMARY.mdafter Installation.English only for now —
fr/leadbay-mcp/has noinstallation.mdand a reduced page set, so EN is the complete MCP-install surface. FR can follow if wanted.Docs-only change; no eval coverage applies.
Closes https://github.com/leadbay/product/issues/3837