Microsoft and Salesforce have launched Copilotforce, an initiative that integrates Salesforce customer data and workflows into Microsoft Copilot and Teams. The partnership uses authenticated MCP access to allow AI agents to act on CRM data while respecting existing security and permissions.
MoEngage has integrated AI agents into its customer engagement platform by using the Model Context Protocol (MCP) and Amazon Bedrock AgentCore to expose existing APIs as agent-callable tools. By treating its platform as an architecture of isolated sessions and standardized tool schemas, the company enabled teams to automate workflows and decision-making within a single conversation.
Amazon introduced a pattern for securing multi-tenant AI agents by ensuring that RAG search queries are scoped to specific users. The solution uses ACL-aware knowledge bases combined with a request interceptor in the AgentCore Gateway to deterministically inject verified user identities into tool calls, preventing LLMs or prompt injections from accessing unauthorized data.
Amazon introduced a serverless Model Context Protocol (MCP) gateway built on Amazon ECS Fargate that allows AI agents to query enterprise data lakes using a metadata-driven approach. Instead of writing custom integration code for every new dataset, you define table schemas and business logic in JSON, which the system automatically registers and indexes.
Amazon introduced Web Answer on Bedrock AgentCore, a managed tool that simplifies agent-based web research. It automates the entire pipeline from searching and verifying facts to synthesizing cited answers, delivering results via MCP.
Mistral AI has launched significant updates to Mistral Studio, a platform designed to take AI projects from pilot to production. It now includes managed agents, advanced workflow orchestration, and enterprise-grade observability, enabling deployment across cloud, VPC, or on-premises environments.
NVIDIA has introduced the AI Factory Operations Agent, a framework built on NemoClaw and OpenShell, designed to automate the management and troubleshooting of large-scale GPU clusters. By leveraging specialized sub-agents and Model Context Protocol (MCP), it enables SREs to perform root cause analysis across hardware, network, and software layers through a unified chat interface.
This update outlines a method for building a semantic knowledge base directly within PostgreSQL using the AIDB extension. By indexing schema metadata and utilizing the Model Context Protocol (MCP), you can expose database tools to agents in Amazon Bedrock AgentCore while enforcing existing row-level security.
Amazon has updated the AgentCore Gateway to support automated token exchange between Microsoft Entra ID and protected REST APIs. By leveraging this flow, AI agents can now perform actions in platforms like ServiceNow using the identity and permissions of the end-user rather than acting as a generic service account.
MoEngage successfully integrated over 400 internal REST APIs as agent tools using Amazon Bedrock AgentCore Gateway. This approach eliminated the need for manual MCP server maintenance, complex networking, and security risks associated with public internet exposure.
Google Cloud has released IAM Helper, a suite of agent-facing building blocks designed to automate complex Identity and Access Management (IAM) workflows. By integrating with Google Cloud's core IAM engines via MCP (Model Context Protocol), these tools enable autonomous agents to handle tasks like troubleshooting 403 errors, simulating policy impacts, and requesting just-in-time access.
Amazon Bedrock AgentCore is a new service designed to streamline the deployment and management of multi-agent architectures. It handles agent hosting, secure tool access via MCP, and session isolation, enabling teams to focus on agent behavior rather than operational overhead.
AWS announced general availability of training sessions within Amazon SageMaker AI serverless model customization. Teams can write their own post-training loops — including custom loss functions and reward signals for reinforcement learning — while SageMaker AI handles GPU allocation, distributed execution, fault recovery, and checkpoint storage. Supported techniques include SFT, DPO, RLVR, RLAIF, and multi-turn RL, and users can choose LoRA or full fine-tuning. The feature supports models including gpt-oss-20b, gemma-4-31B-it, Qwen3.6-27B, and Qwen3.8-27B, and billing is based on tokens processed, pausing while a user's reward function scores responses.
Google announced Public Preview of streaming support in API Gateway, covering Server-Sent Events, chunked/NDJSON responses, WebSockets and gRPC streaming. Streaming endpoints can now sit behind the same gateway as regular APIs, keeping existing authentication, logging and monitoring, without any changes to the API spec. Streams can stay open up to one hour, and gateways now get a predictable default hostname instead of a generated hash. The feature also ties into model routing, letting a single gateway stream responses from Gemini, Claude and OpenAI gpt-oss models.
AWS published a walkthrough for the Adaptive Agentic Intelligence Framework (AAIF), built on Strands Agents, which routes simple requests to small local models (via Ollama) and only sends complex requests to cloud models through Amazon Bedrock. A lightweight 1B-parameter model (llama3.2:1b) acts as an orchestrator deciding where each request should go, with an example IoT monitoring agent that uses local telemetry retrieval, local vision analysis, and cloud-based expert insights. AWS states that in the hybrid setup, roughly 80 percent of traffic can be handled locally without hitting a paid API, and the architecture can run fully on edge hardware (e.g. Raspberry Pi with 8GB memory), fully in the cloud, or in a hybrid mode.
AWS introduced Agent Registry, a managed catalog service for Model Context Protocol (MCP) servers, agents, and agent skills. Instead of hardcoding every tool into an orchestrator, agents can now search an approved, versioned catalog at runtime and build a client from the returned descriptor. A reference sample demonstrates a Discover → Instantiate → Execute loop using Amazon Bedrock AgentCore Gateway and AgentCore runtime, with Anthropic Claude Sonnet as the foundation model.
Eon, a data protection ISV running on AWS, replaced per-tool credentials and local MCP servers with a single Amazon Bedrock AgentCore MCP Gateway. The gateway uses Cedar-based policies to enforce least-privilege access for both human engineers and an autonomous SRE agent running Claude on Amazon Bedrock, routing calls to MCP servers hosted on AgentCore Runtimes across multiple AWS accounts. Developer onboarding time dropped from about two days to about two minutes after rolling the system out to 100+ developers and roughly 10,000 sessions.
AWS and Keyfactor published a reference design that fixes a known weak point in Model Context Protocol (MCP) deployments: MCP has no built-in way to authenticate which agent is actually making a request. The architecture adds three trust layers — user-to-system, agent-to-agent, and agent-to-tool-server — built on signed request envelopes, delegation assertions signed by the user, RFC 8693 audience-restricted tokens, and live OCSP revocation checks. A working example runs on Amazon Bedrock and the AWS Strands Agents SDK with Keyfactor EJBCA issuing and validating the X.509 certificates, and the full code is on GitHub.
Google Cloud published a reference architecture for building AI agents that coordinate long-running, GPU-heavy scientific tasks like protein folding and compound screening, which break standard single-LLM-agent setups due to timeouts and context overflow. The design separates a cognitive orchestrator (Gemini on Agent Runtime) from a GPU execution layer (NVIDIA NIMs like ESMFold and GenMol on GKE) and wraps both in an enterprise governance plane with agent identity, a gateway, a registry and Model Armor. It also lays out best practices such as passing bulky data by reference instead of inline, streaming progress updates, and gating irreversible actions behind human approval.
AWS published a governance framework called Trust in Depth, designed to let AI agents operate with more autonomy while staying within enforceable limits. It combines scoping agent permissions before deployment, giving each agent a verifiable identity, enforcing boundaries at runtime via policy gateways, and observing agent behavior afterward. The framework leans on automated reasoning (mathematical proof) for rules that can be precisely defined, and human judgment for ambiguous cases, using AWS tools like Bedrock AgentCore, Guardrails, Kiro, Strands, Agent Registry and CloudWatch Omni.
Google has released Apigee hybrid 1.17.0 (September 14, 2026), adding Model Context Protocol (MCP) support that runs entirely inside a customer's own Kubernetes cluster rather than on Google-managed infrastructure. This lets organizations with data-residency or regulatory requirements turn existing OpenAPI-described APIs into AI-agent-callable tools without MCP request traffic leaving their network. The feature reuses existing Apigee identity, security policies and API product controls, and it is an optional, off-by-default capability enabled via a Helm chart upgrade.
NVIDIA published a case study showing how Siemens EDA applied its open NeMo Gym evaluation library to tighten up an agentic tool used for chip characterization. Instead of checking individual tool calls, the team scored complete final output files with a domain-specific verifier, then used the failure patterns to rewrite the agent's skill instructions and MCP tool descriptions. After several rounds of this loop, a composite accuracy benchmark climbed from roughly 55% to 95%, while the agent needed far fewer steps and far less output to get there. The experiments relied on about 25 evaluation rollouts running Claude Opus 4.8 as the agent model inside Claude Code.
Google introduced AQuA (Ambient Quality Agent), a tool that runs continuously beside production AI agents inside a Google Cloud project to find failures that don't show up in logs or health checks, such as skipped validation steps or dropped context between sub-agents. It samples production session traces, grades them against a checklist, clusters recurring failure patterns, verifies clusters against full transcripts, and tracks them over time as new, recurring, or resolved. On request, it can also trace a failure back to the exact line of code or prompt responsible, using an immutable source snapshot captured at deploy time.
Google Cloud announced the Gemini agent, a unified agent that combines chat, knowledge work, content creation, and coding into one interface accessible across devices and channels. It integrates directly inside Gmail, Docs, Sheets, Slides, Chat, and Calendar, connects to enterprise tools and databases via MCP and a tools registry, and orchestrates across multiple models — including Google's Gemini family and Anthropic's Claude — to balance quality and cost. Google also detailed security/governance features, cost controls like Smart Routing and spend caps, and shared customer results from companies like BNP Paribas, Bradesco, and Orange Spain.