docs(mcp): add client connection guide

[urjitc]

Summary

• Add a production MCP connection guide to the Mintlify documentation.
• Add the guide to the Guides navigation group.

Why

The production MCP server is live, but the public documentation does not explain how to connect a compatible AI client, authorize workspace access, or understand role-based permissions.

Changes

• Document URL-only OAuth setup for Claude, Cursor, and VS Code.
• Explain workspace selection, read/write capabilities, membership enforcement, and troubleshooting.
• Keep client-specific instructions linked to current primary documentation.

Testing

• Parsed docs/docs.json as JSON.
• Compiled docs/guides/mcp.mdx with @mdx-js/mdx@3.1.1.
• Formatted the MDX with Prettier 3.6.2.
• Passed staged-file checks and git diff --check.

Review Notes

• The unrelated untracked document AI refactor note is intentionally excluded.

---

^{Need help on this PR? Tag /codesmith with what you need. Autofix is disabled.}

[cursor]

Bugbot is not enabled for your account, so this pull request was not reviewed.

Enable Bugbot in the Cursor dashboard to get automatic reviews on future PRs.

[capy-ai]

Capy auto-review is paused for this organization because the usage-cycle auto-review limit has been reached. Increase the limit or turn it off in billing settings to resume automatic reviews.

[mintlify]

Preview deployment for your docs. Learn more about Mintlify Previews.

Project	Status	Preview	Updated (UTC)
thinkex	🟢 Ready	View Preview	Jul 18, 2026, 2:07 AM

[coderabbitai]

Warning

Review limit reached

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

Next review available in: 49 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

Run ID: 7f216e27-ce29-4d72-81d6-27927392e839

📥 Commits

Reviewing files that changed from the base of the PR and between c84d411 and 53ed874.

📒 Files selected for processing (2)

• docs/docs.json
• docs/guides/mcp.mdx

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch codex/mcp-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

• X
• Mastodon
• Reddit
• LinkedIn

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

[cubic-dev-ai]

No issues found across 2 files

<sub>Auto-approved: Adds a new MCP client connection guide to documentation; no code or configuration changes.

Re-trigger cubic</sub>

[greptile-apps]

Greptile Summary

This PR adds public documentation for connecting AI clients to ThinkEx MCP. The main changes are:

• New docs/guides/mcp.mdx guide for Claude, Cursor, and VS Code setup.
• Permission and workspace role behavior documented for MCP access.
• Troubleshooting guidance added for common connection and authorization problems.
• docs/docs.json updated to include the MCP guide in navigation.

Confidence Score: 5/5

This documentation-only change is safe to merge.

The changes are limited to a new MDX guide and one matching navigation entry. The new page path matches the added file, and no correctness or security issues were identified.

No files require special attention.

T-Rex Logs

What T-Rex did

• T-Rex produced a finding-comment-proof for a posted P2 finding.
• T-Rex performed contract validation and generated a main MCP validation log, plus per-command logs for JSON parse, MDX compile, Prettier check, and git diff whitespace check, and copied the MDX harness files for the 3.1.1 compile into artifacts.

_{Ran code and verified through T-Rex}

Important Files Changed

Filename	Overview
docs/docs.json	Adds the new MCP guide to the existing Guides navigation group.
docs/guides/mcp.mdx	Adds a Mintlify MDX guide for connecting MCP-compatible clients, permissions, workspace selection, actions, and troubleshooting.

Comments Outside Diff (1)

1. General comment

   docs/docs.json fails the stated Prettier 3.6.2 formatting check

   • Bug
     • The requested command pnpm dlx prettier@3.6.2 --check docs/docs.json docs/guides/mcp.mdx exited with code 1. Prettier reported [warn] docs/docs.json and Code style issues found in the above file, while the other stated checks passed.
   • Cause
     • docs/docs.json is not formatted according to Prettier 3.6.2's formatting rules.
   • Fix
     • Run pnpm dlx prettier@3.6.2 --write docs/docs.json docs/guides/mcp.mdx and commit the resulting formatting changes, or otherwise update docs/docs.json to match Prettier 3.6.2 output.

   _{Ran code and verified through T-Rex}

_{Reviews (1): Last reviewed commit: "docs(mcp): add client connection guide" | Re-trigger Greptile}