docs: add Cloudflare Agents integration guide

[parvahuja]

Summary

• Add a Cloudflare Agents guide under "Use with partner SDKs": one ~15-line hero where an Agent connects an MCP server and calls free and paid tools through the same client via McpClient.wrap — including the onPaymentRequired spend-policy hook.
• Tempo Accounts access keys are the headline path (provider.mpp.methods, wallet-native wallet_authorizeChallenge authorization when supported); a viem private-key account appears only as a labeled local-development variant.
• Update the McpClient.wrap reference page for the unified in-place API (same reference returned, SDK three-argument callTool preserved, per-call approval hook), plus sidebar entries and quickstart cross-links.

Every code block is compile-verified against the real SDK builds, and the integration is proven end-to-end by a deployed Worker (agent pays $0.01 per tool call on Tempo testnet, receipt with on-chain reference returned).

Dependencies — land last, in this order

1. feat!: unify mcp client payment wrapping into a single McpClient.wrap wevm/mppx#526 (unified McpClient.wrap, mppx/mcp/client entrypoints) released, then bump this repo's mppx dependency.
2. feat(provider): serve wallet_authorizeChallenge and expose provider.mpp accounts#645 (provider.mpp) released, for the Accounts hero path.
3. feat: add wallet_authorizeChallenge support wevm/mppx#540 (wallet_authorizeChallenge client) makes the wallet-native authorization sentence live; the guide works without it via local signing.

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
mpp	Ready	Preview, Comment	Jun 12, 2026 12:15am

[gakonst]

dumb q- this also covers all the fetch-es that the CF agents would do right?