Rename @outblock/cadence-mcp → @onflow/cadence-mcp on npm

[Aliserag]

The MCP server is published to npm as @outblock/cadence-mcp. Outblock was Hao Xu's company namespace; the canonical home for Flow ecosystem packages is the @onflow org.

Steps

1. Confirm @onflow npm org admin can create the package
2. Publish a major-version bump (@onflow/cadence-mcp@2.0.0) with identical bin name (cadence-mcp) + same tool set
3. Update @outblock/cadence-mcp in npm with deprecation notice pointing at the new package
4. Update install snippets across:
   • content/docs/ai-tools/mcp-server.mdx
   • content/docs/ai-tools/integrations/{claude,cursor,codex,gemini,antigravity,opencode}.mdx
   • src/routes/index.tsx (homepage MCP card)
   • mcp-server/package.json
   • All references in pr285-evaluation/ docs
5. Update Cursor deeplink base64 config (eyJjb21tYW5kIjoibnB4IiwiYXJncyI6WyIteSIsIkBvbmZsb3cvY2FkZW5jZS1tY3AiXX0=)

Why now

• Hao left Outblock; @Outblock npm namespace is no longer under Flow Foundation control
• All other Flow packages (@onflow/fcl, @onflow/types, etc.) are in @onflow

Coordinate with whoever owns @onflow npm org admin.

[Aliserag]

Superseded by #306's MCP consolidation. The npm package @outblock/cadence-mcp is no longer the canonical install path; flow mcp (Flow CLI built-in) is. Recommend: npm deprecate @outblock/cadence-mcp@\"*\" "Use 'flow mcp' from the Flow CLI instead — see https://cadence-lang.org/docs/ai-tools/mcp-server" once Flow Foundation has access to the @Outblock npm namespace, or simply leave it published as-is and let flow mcp carry forward as the canonical.