Add secure Web Search to Claude Desktop with Amazon Bedrock AgentCore

Amazon Web Services has extended Claude Desktop beyond its training cutoff by wiring it to live web results through Amazon Bedrock AgentCore Gateway. The integration pairs JWT-based authentication — handled by AWS IAM Identity Center and Amazon Cognito — with the Model Context Protocol so that Claude Desktop can query the open web without exposing credentials or bypassing access controls.

This article walks through what AWS built, how the authentication chain works, and what the setup means for teams already running Claude on Bedrock. It is aimed at platform engineers, AI architects, and developers who need Claude Desktop to answer questions about events that happened after the model's knowledge cutoff.

Secure Web Search to Claude Desktop: what actually changed

Claude Desktop, when connected to Amazon Bedrock, operates entirely within the boundaries of the model's training data. That means questions about recent product releases, regulatory changes, or live market conditions return stale or incomplete answers. AWS addressed this by exposing a web-search capability through Amazon Bedrock AgentCore Gateway, a managed layer that sits between Claude Desktop and external tools. The gateway acts as the single controlled entry point, meaning web search is not bolted directly onto the model but is instead mediated through a structured API surface that inherits Bedrock's existing governance controls.

The change is architectural as much as it is functional. Rather than giving Claude Desktop a raw internet connection, AWS routes search requests through AgentCore Gateway and enforces identity verification before any query leaves the controlled environment. Organizations that have already invested in Bedrock-native guardrails, logging, and cost controls retain those protections even when the model is pulling information from outside its training corpus.

Secure Web Search to Claude Desktop: how it works

The connection relies on the Model Context Protocol, which Claude Desktop uses to discover and call external tools. AWS configures an MCP server endpoint inside AgentCore Gateway, and Claude Desktop registers that endpoint as a tool provider at startup. When a user's prompt requires current information, Claude routes the web-search call through MCP to the gateway rather than attempting direct network access.

Authentication travels through two AWS-managed identity services. AWS IAM Identity Center issues a JWT that vouches for the user's organizational identity, and Amazon Cognito handles token exchange so that the gateway can validate inbound requests without requiring each client to hold long-lived API keys. The gateway then executes the web search, returns structured results to Claude, and the model synthesizes those results into a response. Builders enabling this flow need to configure both the Cognito user pool and the IAM Identity Center application, then register the resulting MCP endpoint in Claude Desktop's configuration file.

Secure Web Search to Claude Desktop: why it matters now

Retrieval-augmented generation systems have long used vector databases to give language models access to private documents, but live web search adds a different capability: access to information that did not exist when either the model or the knowledge base was last updated. For enterprises running Claude on Bedrock, the gap between the model's knowledge cutoff and today's date grows with every passing week, making web grounding increasingly necessary for customer-facing or analyst-facing deployments.

AWS chose JWT-based authentication through managed identity services rather than API-key patterns because it aligns web search with the same identity governance that controls other Bedrock resources. Audit logs, session boundaries, and conditional access policies that an organization has already applied to its Bedrock workloads extend naturally to web-search queries. That alignment reduces the compliance review surface compared with integrating a third-party search provider directly.

Secure Web Search to Claude Desktop: who is affected

Teams building internal assistants, research tools, or support automation on Claude Desktop through Bedrock are the primary audience. If those deployments currently answer only from static knowledge, adding AgentCore Gateway web search changes the response quality for any prompt that touches recent events, version changes, or live documentation. Security and compliance teams will need to review the Cognito pool configuration and confirm that the IAM Identity Center application is scoped to the correct organizational units before rollout.

Developers who have already built MCP integrations for other Bedrock tools will find the pattern familiar. The gateway endpoint registration follows the same MCP configuration structure, so the incremental work is primarily in identity plumbing rather than protocol changes. Organizations that do not use IAM Identity Center today will need to stand up that service before they can complete the JWT authentication chain the architecture requires.

Secure Web Search to Claude Desktop: what to watch

The current architecture routes web search through AgentCore Gateway, which means search result quality and latency depend on both the gateway's upstream search provider and the network path between Bedrock and that provider. Teams evaluating the setup should measure round-trip latency under realistic query volumes and check whether the gateway's search results include the sources Claude's jurisdiction requires for citations or grounding transparency.

On the identity side, JWT expiry and token refresh behavior under long-running Claude Desktop sessions is worth validating before production use. If a session outlasts the token's validity window without a seamless refresh, users will encounter authentication failures mid-conversation. AWS's managed services handle much of this automatically, but integration teams should verify that the Cognito token-refresh flow is configured and tested end-to-end in their specific organizational setup before enabling the capability for a broad user base.