Integrate MCP Cadence server into Flow CLI

[peterargue]

Summary

Integrate the MCP Cadence server into the Flow CLI, resolving the local vs. remote approach and maintaining a single source of truth.

Context

Peter has a Flow CLI MCP PR (#2306) that wraps CLI functionality for AI agent access. Hao's version does the same except for docs. The MCP currently lacks Cadence and Flow doc search ability. We need to decide on the integration approach (local vs remote) and close the docs gap, potentially via Context7 or a dedicated skill.

Key considerations:

• Local use case is more common than remote
• Remote option would wrap Flow CLI in an API as a remote service
• Need to close the docs gap (Context7 or skill-based approach)
• CLI --agent flag to make the CLI skill discoverable by agents

Acceptance Criteria

• MCP Cadence server integrated into Flow CLI
• Docs gap addressed (via Context7, skill, or built-in)
• Local usage works out of the box
• CLI --agent flag implemented for agent discoverability
• Single source of truth maintained between CLI and MCP

References

• Flow CLI MCP PR #2306
• Slack thread
• Discussed in AI tooling sync (Apr 1)