Skip to content

fix: point MCP links to docs /surfaces/mcp instead of /cli/login - #17

Open
laxman-patel wants to merge 1 commit into
mainfrom
fix/mcp-link-docs
Open

laxman-patel wants to merge 1 commit into
mainfrom
fix/mcp-link-docs

Conversation

@laxman-patel

Copy link
Copy Markdown
Owner

What

Both ...or connect with MCP links on the landing page (apps/web/app/page.tsx) pointed at /cli/login. They now open ${docsUrl()}/surfaces/mcp in a new tab, matching the footer Docs link.

Why

Maria found that the MCP links went to the CLI login page instead of the MCP docs surface. The intended destination is the MCP docs page (same as the footer docs link, opened in a new tab).

Changes

  • Added const mcpDocsHref = \${docsUrl()}/surfaces/mcp`;next to the existingdocsHref`.
  • Hero CTA link: href="/cli/login"href={mcpDocsHref} target="_blank" rel="noopener noreferrer".
  • Final CTA link: same change.

Tiny diff — 1 file, 3 lines. No other lines touched.

Verification

  • next dev renders / with 200; both MCP links now render href="https://docs.hostartifacts.dev/surfaces/mcp" and no /cli/login href remains.
  • Video proof attached shows clicking an MCP link and landing on the MCP docs page.
  • Typecheck: no new errors introduced (pre-existing workspace-package typecheck errors are unrelated).

Both '...or connect with MCP' links on the landing page (hero and final
CTA) pointed at /cli/login. They now open the MCP docs surface in a new
tab, matching the footer Docs link.
@coderabbitai

coderabbitai Bot commented Jul 9, 2026

Copy link
Copy Markdown

Warning

Review limit reached

@laxman-patel, you've reached your PR review limit, so we couldn't start this review.

Next review available in: 20 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details
⚙️ Run configuration

Configuration used: defaults

Review profile: CHILL

Plan: Pro Plus

Run ID: 285518b3-79d3-438a-8d84-ed8ae5a2553f

📥 Commits

Reviewing files that changed from the base of the PR and between c0283af and 74e90bc.

📒 Files selected for processing (1)
  • apps/web/app/page.tsx
✨ Finishing Touches
🧪 Generate unit tests (beta)
  • Create PR with unit tests
  • Commit unit tests in branch fix/mcp-link-docs

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands.

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant