AIToday
Large Language ModelsTHE DECODERPublished: Jul 9, 2026, 01:00 JST

Google Deepmind adds background execution and MCP support to Gemini API agents

Google Deepmind adds background execution and MCP support to Gemini API agents

3 Key Points

  1. What happened

    Google Deepmind has added four new capabilities to Managed Agents in the Gemini API: Background Execution (allowing agents to run asynchronously without an open HTTP connection), direct connection to remote MCP servers for internal databases or APIs, support for custom functions alongside built-in sandbox tools, and automatic credential refresh between interactions.

  2. Why it matters

    These additions expand what developers can build with Gemini's agent framework, removing the constraint of keeping an HTTP connection open and enabling deeper integration with existing enterprise systems and data sources through MCP protocols.

  3. What to watch

    All features are available now through the Gemini Interactions API, with code examples provided for JavaScript, Python, and cURL in the documentation.

Not sure about something? Ask the AI

Questions and answers are published on this page.

Summaries like this, in your inbox every morning.

Context & Analysis

Google Deepmind's expansion of the Gemini API's Managed Agents addresses practical bottlenecks in agent deployment. The Background Execution feature removes a technical constraint—the requirement to maintain an open HTTP connection—that would have otherwise forced developers to keep resources allocated for the duration of an agent's work. This is particularly valuable for long-running tasks where maintaining an active connection would be inefficient.

The addition of remote MCP (Model Context Protocol) support signals a strategic move toward interoperability with existing enterprise systems. MCP is an emerging standard for connecting AI systems to external tools and data sources; by allowing agents to connect directly to internal databases and APIs through MCP, Google is positioning Gemini agents as components that can integrate into mature software stacks without heavy custom middleware. The ability to refresh credentials between interactions without resetting sandbox state preserves security and statefulness—two concerns that can otherwise force developers to choose between convenience and safety.

Together, these changes lower friction for developers building production agent applications, particularly those working within organizations with existing database and API infrastructure that they want agents to access safely and persistently.

FAQ
What new capabilities can developers use with these updates?
Developers can now run agents asynchronously in the background using Background Execution with no open HTTP connection required, connect remote MCP servers directly to internal databases or APIs, use custom functions alongside built-in sandbox tools, and refresh credentials like tokens between interactions without losing the sandbox state.
Which programming languages are supported?
Code examples are available for JavaScript, Python, and cURL in the documentation.

AI news that matters for your work, delivered every morning.

Pick your industry and the AI tools you use, and get news related to your work every day.

Free · 30 seconds with Google · unsubscribe anytimeWhat is AIToday? →

Ask AI

Ask AI anything about this article. The AI reads this article, earlier AIToday articles, and Wikipedia, and cites its sources. Q&As are published on this page for other readers too.

Questions and answers are published on this page.

Related Articles

Next articleGitHub Copilot CLI automates DNS setup for custom domains in 14 minutes