# MCP server

Google released chrome-devtools-mcp, which lets coding agents such as Antigravity, Claude, Cursor and Copilot control and inspect a running Chrome browser through a Model-Context-Protocol server or a command-line interface. It hands agents DevTools performance tracing, network request analysis, screenshots and console messages, and uses puppeteer to perform actions and automatically wait for their results. The tool officially supports only Google Chrome and Chrome for Testing; other Chromium-based browsers may work but are not guaranteed.

Google released chrome-devtools-mcp, which lets coding agents such as Antigravity, Claude, Cursor and Copilot control and inspect a running Chrome browser through a Model-Context-Protocol server or a command-line interface. It hands agents DevTools performance tracing, network request analysis, screenshots and console messages, and uses puppeteer to perform actions and automatically wait for their results. The tool officially supports only Google Chrome and Chrome for Testing; other Chromium-based browsers may work but are not guaranteed.

Mastra has added tasks to its MCP server and client so that long-running tool calls run in the background. Previously MCP tool calls were synchronous: a single HTTP request stayed open until the call finished, blocking the agent loop, and although Mastra's existing background tasks primitive could free the loop, a call that outlasted a proxy timeout or a load balancer's idle limit would still fail. Now the server returns a task ID that ends the request, the client polls that ID for working, input_required, completed, failed or cancelled status, and a notification signal reaches the agent when the task completes.

Mastra has added tasks to its MCP server and client so that long-running tool calls run in the background. Previously MCP tool calls were synchronous: a single HTTP request stayed open until the call finished, blocking the agent loop, and although Mastra's existing background tasks primitive could free the loop, a call that outlasted a proxy timeout or a load balancer's idle limit would still fail. Now the server returns a task ID that ends the request, the client polls that ID for working, input_required, completed, failed or cancelled status, and a notification signal reaches the agent when the task completes.

Databricks released Genie plugins that let agents in ChatGPT, Claude, Microsoft Copilot Cowork and Grok Bot reach enterprise context through the Genie MCP server. Previously an agent facing a business question started a live search, hopping between MCP servers, opening documents and trying tables with little sense of where the right answer lived. With the plugin, Genie interprets business terms through Genie Ontology, finds data the user is allowed to see, writes and runs SQL, and returns an answer with citations, routing to domain Genie Agents when needed.

Databricks released Genie plugins that let agents in ChatGPT, Claude, Microsoft Copilot Cowork and Grok Bot reach enterprise context through the Genie MCP server. Previously an agent facing a business question started a live search, hopping between MCP servers, opening documents and trying tables with little sense of where the right answer lived. With the plugin, Genie interprets business terms through Genie Ontology, finds data the user is allowed to see, writes and runs SQL, and returns an answer with citations, routing to domain Genie Agents when needed.

Anthropic built a reference implementation of a scheduled agent automation on Claude Managed Agents (beta): it reads Slack channels and GitHub pull requests from per-source bookmarks, reports only what changed since the last run, and posts the result to one Slack channel. Against the usual failures of scheduled jobs, the configuration keeps a source's bookmark when a read fails and names that source as unreadable at the end of the brief, and it updates bookmarks and its ledger only after Slack confirms a post.

Anthropic built a reference implementation of a scheduled agent automation on Claude Managed Agents (beta): it reads Slack channels and GitHub pull requests from per-source bookmarks, reports only what changed since the last run, and posts the result to one Slack channel. Against the usual failures of scheduled jobs, the configuration keeps a source's bookmark when a read fails and names that source as unreadable at the end of the brief, and it updates bookmarks and its ledger only after Slack confirms a post.

Vercel Labs has released agent-browser, a native Rust command-line tool that lets an AI agent drive a browser one shell command at a time. Previously an agent had to work from the whole page; now snapshot returns the page as compact text with a ref such as @e1 for each element, and the agent acts on a ref, reads the page again to check the result, and repeats. The browser stays open between commands, so each step is one short shell call, and a click fails rather than reporting success when the target is hidden, disabled, outside the viewport, or covered.

Vercel Labs has released agent-browser, a native Rust command-line tool that lets an AI agent drive a browser one shell command at a time. Previously an agent had to work from the whole page; now snapshot returns the page as compact text with a ref such as @e1 for each element, and the agent acts on a ref, reads the page again to check the result, and repeats. The browser stays open between commands, so each step is one short shell call, and a click fails rather than reporting success when the target is hidden, disabled, outside the viewport, or covered.

Mastra's @mastra/mcp 2.0 now supports the MCP 2026-07-28 specification, which removes server sessions so every request is self-contained. Under the previous spec a client opened each connection with an initialize request, the server returned a session ID, and later requests had to carry it; a load balancer routing to another instance produced 400 session not found errors, worked around with sticky sessions or a shared store such as Redis. Now any instance can answer any request, a round-robin balancer suffices, and if an instance crashes the next request goes elsewhere while the client continues.

Mastra's @mastra/mcp 2.0 now supports the MCP 2026-07-28 specification, which removes server sessions so every request is self-contained. Under the previous spec a client opened each connection with an initialize request, the server returned a session ID, and later requests had to carry it; a load balancer routing to another instance produced 400 session not found errors, worked around with sticky sessions or a shared store such as Redis. Now any instance can answer any request, a round-robin balancer suffices, and if an instance crashes the next request goes elsewhere while the client continues.