[docs] Plan MCP product features after Pi parity

[mmabrouk]

Context

The MCP contract cleanup makes external HTTP configuration truthful, but it intentionally does not add connection testing, discovery, visible status, enforceable tool selection, OAuth, or a platform gateway. Pi support is also an immediate slice 2.2 prerequisite, not something this plan silently folds into a late gateway phase.

Changes

This docs-only planner-feature workspace defines the product-feature work that starts after Claude acceptance and the Pi 2.2 delivery design:

• test connections through the same client path used by execution;
• return redacted initialization status and discovered tool schemas;
• select real discovered tools and enforce policy on both list and call;
• add static secret references and OAuth without storing values in agent revisions;
• compare direct per-harness MCP clients with a platform gateway before choosing the long-run execution owner;
• verify Claude and Pi across local and Daytona before publishing capabilities.

The saved role-based MCP object remains unchanged. Public stdio, compatibility logic, and feature flags remain out of scope.

Tests / notes

• Docs-only change with seven self-contained planning files.
• The plan explicitly depends on slices 0-2, Claude acceptance, and Pi slice 2.2.
• Gateway is an open architectural decision with concrete evaluation criteria, not a preselected implementation.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
agenta-documentation	Ready	Preview, Comment	Jul 13, 2026 8:48pm

[coderabbitai]

Important

Review skipped

Draft detected.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro Plus

Run ID: 719cc1a0-b3aa-49c2-ba64-068f3df074ca

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch docs/mcp-product-features-plan

---

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.}

[mmabrouk]

🤖 The AI agent says:

Closing this plan as redundant, per review. It does not establish a new decision or implementation boundary beyond the existing MCP redesign plan. The useful clarification is now carried by PR #5290 and its interface documentation: the current slice is direct external HTTP MCP delivery, while Pi parity and any later gateway decision remain separate follow-up work.