Skip to content

fix: point landing page MCP links to docs/surfaces/mcp#18

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

fix: point landing page MCP links to docs/surfaces/mcp#18
laxman-patel wants to merge 1 commit into
mainfrom
fix/mcp-link-destination

Conversation

@laxman-patel

Copy link
Copy Markdown
Owner

What

Both "...or connect with MCP" links on the landing page (apps/web/app/page.tsx) were pointing to /cli/login instead of the MCP docs page.

Fix

Changed both links (hero section + final CTA) to open `${docsUrl()}/surfaces/mcp` in a new tab (target="_blank" rel="noopener noreferrer"), matching the pattern already used by the footer Docs link.

Diff

-<Link href="/cli/login" className="...">
+<Link href={`${docsHref}/surfaces/mcp`} target="_blank" rel="noopener noreferrer" className="...">
   ...or connect with MCP <span aria-hidden>↗</span>
 </Link>

Applied to both occurrences (lines 375 and 507).

Verification

  • Dev server confirmed both links now render href="https://docs.hostartifacts.dev/surfaces/mcp" with target="_blank".
  • No more /cli/login links remain on the page.
  • Video proof recorded showing the landing page and the docs/surfaces/mcp destination.

Both "...or connect with MCP" links on the landing page were going to
/cli/login instead of the MCP docs page. They now open
${docsUrl()}/surfaces/mcp 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: 58 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: 6477044b-b205-4471-bfdf-e6b46db4fb70

📥 Commits

Reviewing files that changed from the base of the PR and between c0283af and 3d8e5e8.

📒 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-destination

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.

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