Document Composio as a companion MCP path

[AojdevStudio]

What to build

Document Composio as a companion MCP/tool provider for connected-account workflows while preserving the Google Workspace MCP Worker boundary. The documentation should make clear that Composio owns connected-account OAuth and tool execution for Composio-connected accounts, while this repo remains the self-hosted Cloudflare Workers Google Workspace MCP runtime.

Acceptance criteria

• The docs explain that Composio is a separate MCP surface, not part of the Google Workspace MCP Worker runtime.
• The docs state that all Composio-supported tools are exposed for the first pass.
• The docs describe when agents should use Composio versus google-workspace.
• The docs avoid listing private mailbox inventories or raw email addresses.
• The guide index links to the Composio companion MCP guide.

Blocked by

None - can start immediately

[linear]

GDRIVE-33