docs(mcp): all-clients installation page + slimmer quickstart#14
Merged
Conversation
…de Desktop - New leadbay-mcp/installation.md: step-by-step for Claude Desktop, Claude.ai, Claude Code, ChatGPT, and Codex, using the remote endpoint https://mcp.leadbay.app/mcp (no tokens; browser OAuth). - quickstart.md now covers just the Claude Desktop one-click path and links out to Installation for the other clients. - SUMMARY.md: add Installation after Quickstart. - Fix stale leadbay/leadclaw repo link in what-is-leadbay-mcp.md -> leadbay/mcp. Co-Authored-By: Claude <noreply@anthropic.com>
…sktop All install paths now go through the remote connector (https://mcp.leadbay.app/mcp) — no extension download. Claude Desktop uses Settings → Connectors → Add custom connector like Claude.ai. Quickstart now opens with the remote-connector flow instead of the .dxt extension. Co-Authored-By: Claude <noreply@anthropic.com>
Full step-by-step for the ChatGPT custom-app (MCP) flow with 8 screenshots (workspace menu → Settings → Apps → Advanced → Developer mode → Create app → Server URL https://mcp.leadbay.app/mcp + OAuth → Sign in), plus a "connection problem" reconnect path (app ⋯ menu → Reconnect, 2 screenshots). Co-Authored-By: Claude <noreply@anthropic.com>
GitBook fails to render <figure> blocks with an empty <figcaption></figcaption> (every other page wraps caption text in <p>…</p>). Add a short <p> caption to each ChatGPT step image so they show in the rendered docs. Co-Authored-By: Claude <noreply@anthropic.com>
…k + admin note - Claude.ai section: direct deep link (claude.ai/customize/connectors?modal=add-custom-connector), 4 screenshots (+ menu, add-connector form, directory, Connect), and a non-admin note — org admins must add the connector before members can connect. - Claude Desktop points to the same connector flow. - Quickstart step 1 gets the direct link + admin note. 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.
Adds a dedicated, step-by-step Installation page covering every assistant, and slims the Quickstart down to the recommended Claude Desktop path.
What changed
leadbay-mcp/installation.md— one section per client: Claude Desktop, Claude.ai, Claude Code, ChatGPT, Codex. Uses the live remote endpointhttps://mcp.leadbay.app/mcp(browser OAuth, no tokens), with a US-vs-EU note and a combined troubleshooting table.quickstart.md— now just the Claude Desktop one-click flow + a link out to Installation for other clients.SUMMARY.md— Installation added right after Quickstart in the Leadbay MCP section.what-is-leadbay-mcp.md— fixed the staleleadbay/leadclawrepo link toleadbay/mcp(the repo was renamed).All commands/URLs were verified live against the deployed server (
mcp.leadbay.app, theclaude mcp add/codex mcp addflows, and the Claude.ai custom-connector path).Closes https://github.com/leadbay/product/issues/3828