Skip to content

[pull] main from google:main#38

Merged
pull[bot] merged 1 commit into
Android-studio61:mainfrom
google:main
May 23, 2026
Merged

[pull] main from google:main#38
pull[bot] merged 1 commit into
Android-studio61:mainfrom
google:main

Conversation

@pull
Copy link
Copy Markdown

@pull pull Bot commented May 23, 2026

See Commits and Changes for more details.


Created by pull[bot] (v2.0.0-alpha.4)

Can you help keep this open source service alive? 💖 Please sponsor : )


Summary by cubic

Refreshes the e2a integration docs to add a Remote MCP Server option and document seven previously missing tools, aligning the page with the current e2a MCP server capabilities.

  • New Features
    • Added “Remote MCP Server” examples for Python and TypeScript using Streamable HTTP with Authorization: Bearer <API_KEY>.
    • Documented new tools: update_agent, delete_agent, get_attachment_data, list_domains, register_domain, verify_domain, delete_domain.
    • Clarified config and prerequisites: Node.js 18+ is only for the local MCP server; E2A_AGENT_EMAIL is only needed for multi-agent accounts; E2A_BASE_URL applies to the local server only.
    • Simplified cloud-mode guidance and linked a verified webhook example; noted HMAC signature verification.

Written for commit 7d0a76a. Summary will update on new commits. Review in cubic

* 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>
@pull pull Bot locked and limited conversation to collaborators May 23, 2026
@pull pull Bot added the ⤵️ pull label May 23, 2026
@pull pull Bot merged commit 7d0a76a into Android-studio61:main May 23, 2026
1 check passed
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant