fix: add 301 redirect from /CLI/mcp to home page

[devin-ai-integration]

Summary

Adds a permanent 301 redirect from /CLI/mcp to the home page to fix a 404 error appearing in Google search results for "agentuity mcp".

Review & Testing Checklist for Human

• After deployment, verify that visiting https://agentuity.dev/CLI/mcp redirects to the home page with a 301 status code

Notes

• Link to Devin run: https://app.devin.ai/sessions/e3e325bbaf1443eca607b54a09418b61
• Requested by: Rick Blalock (@rblalock)

Summary by CodeRabbit

• Chores
  • Implemented URL routing improvements to redirect legacy documentation paths to the main homepage for streamlined navigation.

_{✏️ Tip: You can customize this high-level summary in your review settings.}

[devin-ai-integration]

🤖 Devin AI Engineer

I'll be helping with this pull request! Here's what you should know:

✅ I will automatically:

• Address comments on this PR. Add '(aside)' to your comment to have me ignore it.
• Look at CI failures and help fix them

Note: I can only respond to comments from users who have write access to this repository.

⚙️ Control Options:

• Disable automatic comment and CI monitoring

[coderabbitai]

📝 Walkthrough

Walkthrough

A permanent redirect rule is added to the Next.js configuration file, routing requests from /CLI/mcp to the root path /. This change affects only the redirects configuration with no modifications to other settings or error handling behavior.

Changes

Cohort / File(s)	Summary
Configuration Updates next.config.mjs	Added permanent redirect rule mapping /CLI/mcp to / in the redirects array

🚥 Pre-merge checks | ✅ 1

✅ Passed checks (1 passed)

Check name	Status	Explanation
Description Check	✅ Passed	Check skipped - CodeRabbit’s high-level summary is enabled.

_{✏️ Tip: You can configure your own custom pre-merge checks in the settings.}

---

📜 Recent review details

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between 4523f79 and 8ca10c4.

📒 Files selected for processing (1)

• next.config.mjs

🔇 Additional comments (1)

next.config.mjs (1)

11-15: The proposed fix won't work: statusCode: 301 is not valid syntax in next.config.mjs redirects.

permanent: true correctly returns HTTP 308 in Next.js. However, statusCode: 301 cannot be set in next.config redirects—they only support the permanent boolean flag (true → 308, false → 307). If a 301 redirect is genuinely required, implement it as a server-side redirect using getStaticProps, getServerSideProps, or a route handler instead, not in next.config.

Likely an incorrect or invalid review comment.

_{✏️ Tip: You can disable this entire section by setting review_details to false in your review settings.}

---

_{Comment @coderabbitai help to get the list of available commands and usage tips.}