Anthropic adds remote MCP support to Claude Code

Anthropic announced remote Model Context Protocol support in Claude Code. The company said developers could connect Claude Code to remote MCP servers by adding a vendor URL instead of operating local servers. The release described access to exposed tools and resources, examples involving Sentry and Linear, and native OAuth support. It presented remote servers as a lower-maintenance connection option, while vendors retain responsibility for their services.

Original source date: . Hypler briefing published October 6, 2026.

Topics: Anthropic, MCP, Claude Code, OAuth

Anthropic logo

Generated illustration of modular compute gates and an isolated coding workflow.
Generated illustration of modular compute gates and an isolated coding workflow. Credit: Hypler / AI-generated editorial illustration. Hypler editorial asset; not vendor or event photography
Generated illustration of isolated tool-execution fixtures and a controlled test gate; not deployed software.
Generated illustration of isolated tool-execution fixtures and a controlled test gate; not deployed software. Credit: Hypler / AI-generated editorial illustration. Hypler editorial asset; not vendor or event photography

Engineering relevance

Remote tool connections make the provider, identity, scopes, and server behavior part of an agent's operating boundary. A URL-based setup is not a trust decision by itself. Teams still need to review what each server exposes, which identity is used, where credentials are stored, and how actions or data access are logged and constrained.

Remote server connection

Anthropic said Claude Code could use tools and resources exposed by a remote MCP server, including context from third-party developer and project-management systems. The announcement used Sentry and Linear as examples. It described remote servers as an alternative to maintaining a local MCP process for each connected service.

Identity and ownership

The post said Claude Code included native OAuth support for remote MCP servers, with authentication handled through the connected server. Anthropic also noted that vendors handle their own updates, scaling, and availability. Those boundaries leave scope design, server trust, and action review as separate engineering decisions.

Original source

This is a historical source briefing, not a statement of current availability or Hypler deployment.