* docs(integrations): refresh e2a — hosted endpoint + 7 missing tools
The e2a integration page has drifted from what the e2a MCP server
actually ships. Two gaps this PR closes:
1. **Hosted endpoint not documented.** e2a runs a hosted Streamable
HTTP MCP at https://mcp.e2a.dev/mcp that accepts an API key in
the Authorization header. The page currently only shows the
stdio path (npx -y @e2a/mcp-server), which doesn't work for ADK
agents deployed to Cloud Run since Cloud Run can't host stdio
MCP child processes. Adds a "Hosted MCP Server" tab to both the
Python and TypeScript code examples using
StreamableHTTPConnectionParams.
2. **7 tools missing from the table.** The MCP server now registers
18 tools but the page lists 11. Adds:
Identity: update_agent, delete_agent
Messages: get_attachment_data
Domains: list_domains, register_domain, verify_domain,
delete_domain (new section)
Also clarifies a few descriptions:
- `whoami` notes E2A_AGENT_EMAIL is only required for multi-agent
accounts (the hosted endpoint auto-resolves the sole agent at
session init).
- `delete_agent` and `delete_domain` flag the `confirm: true`
required arg.
- `get_attachment_data` uses 0-based `attachment_index`, not an
attachment ID.
- `E2A_BASE_URL` clarifies the var has no effect when connecting
to the public hosted endpoint.
Cross-linked the cloud-mode webhook example (already shipped in
the e2a repo, not previously referenced from this page) and the
hosted endpoint URL under Additional resources.
No frontmatter / catalog metadata changes — title, description,
icon, and tags (`["mcp"]`) all unchanged.
* fix: import McpToolset from deep path (google-adk 2.0 compat)
google-adk 2.0 stopped re-exporting McpToolset from
`google.adk.tools.mcp_tool`'s package __init__ — only the deep path
`google.adk.tools.mcp_tool.mcp_toolset.McpToolset` still works.
Caught when I actually ran the example against a fresh
google-adk 2.0 install:
ImportError: cannot import name 'McpToolset' from
'google.adk.tools.mcp_tool'
($VENV/site-packages/google/adk/tools/mcp_tool/__init__.py)
Applies to both the stdio code block and the new hosted code block.
StdioConnectionParams and StreamableHTTPConnectionParams already use
deep paths and continue to work — only McpToolset was broken.
* Revert McpToolset import to standard path
The claim that google-adk 2.0 stopped re-exporting McpToolset from
google.adk.tools.mcp_tool is incorrect. The __init__.py at
src/google/adk/tools/mcp_tool/__init__.py explicitly re-exports
McpToolset (and MCPToolset) via `from .mcp_toolset import McpToolset`.
It has done so in every release, including v2.0.0.
* Rename tab to Remote MCP server for consistency with all other integration pages
* Remove link to raw MCP endpoint
* Match API key variable / format with all other integration pages
* Formatting and consistency edits
---------
Co-authored-by: Kristopher Overholt <koverholt@google.com>
* Add e2a integration
e2a is an authenticated email gateway for AI agents — SPF/DKIM-verified
inbound, optional human-in-the-loop approval before outbound mail
ships. Distributed as an MCP stdio server via npx -y @e2a/mcp-server,
exposing 11 tools for inbox management, threaded replies, and HITL
approval flows.
Source: https://github.com/Mnexa-AI/e2a/tree/main/mcp
npm: https://www.npmjs.com/package/@e2a/mcp-server
* docs(e2a): shorten catalog_description per review feedback
Josh Zhang