WWDC 2026 confirmed system-wide MCP support in iOS 27 and macOS 27. Siri 2.0 — the rebuilt, Gemini-backed assistant shipping in September — can invoke MCP servers registered on a device. Core AI, the framework replacing Core ML for generative inference, treats MCP as a first-class routing target.

MCP went from an IDE protocol (Xcode 26.3, February 2026) to an OS-level primitive in four months.

If you operate a public MCP server today, you just got a new client class: iPhones and Macs running iOS 27 and macOS 27.

What Was Announced at WWDC 2026

The system-wide MCP extension ships as part of the iOS 27 and macOS 27 SDK. Key confirmed capabilities:

Siri 2.0 can invoke registered MCP servers. When a user’s request requires information or action that an MCP server provides, Siri will call that server. This is not automatic — servers must be registered (see below) — but the plumbing is now in the OS.

Core AI routes to MCP as a target. Apps using Core AI can declare MCP server endpoints as tool targets. When the system decides a request needs an external tool, it routes to registered MCP servers alongside the user’s chosen Extension (Claude, ChatGPT, Gemini) or Apple’s own cloud models.

MCP clients in the system framework. Before WWDC 2026, MCP on Apple devices required third-party frameworks or custom client implementations. iOS 27 ships an MCP client in the system SDK. Any app can connect to an MCP server using Apple’s own client, handling transport, authentication, and session management.

A dedicated WWDC session: “MCP in Apple platforms” is listed in the WWDC26 session catalog at developer.apple.com/wwdc26. The session covers server registration, capability declarations, and security requirements.

Context: Where MCP Was Before Today

To understand why this matters, the timeline:

November 2024: Anthropic publishes the MCP specification. MCP defines a standardized client-server protocol for AI systems to call external tools, read resources, and use prompt templates.

Early 2025: Major platforms adopt the protocol. Claude, ChatGPT, Gemini, and most agentic frameworks begin shipping MCP clients. The server ecosystem grows rapidly — today, MCP servers exist for GitHub, Stripe, Figma, PostgreSQL, Slack, Kubernetes, and hundreds of other tools.

February 2026 (Xcode 26.3): Apple ships MCP support in Xcode. The IDE exposes 20 built-in tools via an MCP server — file system operations, build and test controls, diagnostics, and Apple documentation search. Claude Code and OpenAI Codex both connect via this MCP surface. This is the first MCP support in any Apple product.

June 2026 (WWDC 2026 / iOS 27 / macOS 27): MCP moves from the IDE to the operating system. The protocol is now a system-level API, accessible to any app on a compatible Apple device.

The jump is significant. Xcode’s MCP server was for developers using AI coding tools. System-wide MCP is for every app, invokable by the platform assistant and the on-device AI framework.

How MCP Server Registration Works in iOS 27

The iOS 27 MCP model requires explicit registration. Siri will not scan for arbitrary servers — registration gates what can be invoked and by whom.

Three registration paths:

1. App-Bound MCP Servers

An app declares its own MCP server in its manifest. When a user installs the app, the server becomes available to Siri and Core AI for tasks related to that app’s domain.

Example: A task management app declares an MCP server with tools like list_tasks, create_task, complete_task. Once installed, a user can say “Hey Siri, add a task to [App Name]” and Siri routes to the app’s MCP server without requiring Shortcuts automation.

This is the lowest-friction path for app developers. The registration is automatic at install. The scope is bounded to the app’s declared domain.

2. Enterprise MDM Registration

Organizations managing Apple devices via MDM can push MCP server registrations to devices. An enterprise MCP server — providing access to internal tools, company data, or workflow systems — can be registered across a fleet without any end-user action required.

This is the enterprise path. A Salesforce MCP server, a Jira MCP server, or an internal knowledge base MCP server can be registered organization-wide and made available to Siri for employees.

MDM registration gives security teams control over which servers employees’ devices connect to. This matters: system-wide MCP without MDM control would be a security gap for enterprise deployments.

3. User-Registered Remote Servers

Users can manually register MCP servers in Settings → Apple Intelligence & Siri → MCP Servers. This requires entering a server URL, an authentication method, and optionally a capability scope.

This is the path for power users who want to connect external tools to their personal Siri. A developer who runs their own MCP server for personal productivity can register it on their own device.

Apple has not yet specified whether user-registered servers will be open to arbitrary endpoints or restricted to a verified server registry. The developer beta documentation is the source of truth.

What Core AI’s MCP Integration Adds

Siri invoking MCP servers is the headline. The Core AI integration is the deeper builder story.

Core AI replaces Core ML as Apple’s on-device generative inference framework. Apps built on Core AI describe a capability requirement — summarize this content, extract these fields, answer this question — and Core AI decides where to run it:

  • On-device Foundation Models (Apple’s distilled model, running locally)
  • Apple’s cloud models via Private Cloud Compute
  • The user’s chosen Extension (Claude, ChatGPT, or Gemini)
  • A registered MCP server

That last option is new. Before iOS 27, on-device AI in apps had three routing options. With system-wide MCP, apps have a fourth: declare an MCP server as a tool target and let Core AI handle the routing decision.

This means MCP servers can now serve as tool backends for any iOS app that adopts Core AI — not just agentic coding tools or AI assistant apps. Any app that does AI work through Core AI can call MCP endpoints as part of its inference routing.

Builder Opportunities This Creates

App Developers: Expose Your App’s Data to Siri

The highest-leverage action for most iOS developers is implementing an app-bound MCP server. The implementation is not complex:

  • Define your tools: what can Siri ask your app to do?
  • Implement the MCP server (Apple’s system SDK now handles transport)
  • Declare the server in your app manifest
  • Handle authentication (the system manages session tokens for registered apps)

Once live, users gain natural language access to your app’s functionality without needing to open the app. For productivity apps, utilities, and anything that manages data or performs actions, this is a meaningful new surface.

The WWDC26 session “Build apps with Apple Intelligence Extensions” covers the Extension SDK. The “MCP in Apple platforms” session covers MCP server registration. Both are available in the session catalog now.

API and Tool Builders: Your MCP Server Is Now Mobile-Eligible

If you already operate a public MCP server — or you’ve built one for a popular API — iOS 27 makes your server potentially reachable by Siri. The gap between “runs in Claude Desktop” and “works on an iPhone” just narrowed considerably.

The constraints are real (see below), but for servers that already handle structured tool calls with deterministic responses, the transition to supporting iOS clients should be low effort once the SDK details are clear.

Enterprise Builders: MDM-Registered MCP as the Enterprise AI Layer

Enterprise organizations now have a path to deploy internal MCP servers as a company-wide AI tool layer on Apple devices. Employees can ask Siri questions that route to internal systems without requiring custom iOS apps for each backend.

An internal knowledge base, a CRM server, a ticketing system, a time tracking tool — any system with an MCP server can become a Siri-invokable tool for employees on managed devices.

This is a different value proposition from public MCP servers. The enterprise MDM path is about controlled, auditable access to internal data through the platform assistant — with IT maintaining the ability to add, update, or revoke server registrations at the fleet level.

Mobile-First MCP: What Changes at Scale

MCP was designed in a desktop/server context. Running at iOS scale introduces constraints that server builders need to plan for:

Latency tolerance is lower. A CLI-based MCP session can wait several seconds for a response. A Siri interaction has a sub-2-second user expectation. Servers invoked via iOS MCP need fast response times. Servers with complex retrieval pipelines or slow external dependencies will need optimization before they deliver good Siri experiences.

Offline behavior needs explicit handling. iOS devices go offline. An app-bound MCP server should declare offline capability clearly in its manifest, so Core AI does not route to it when no network is available. Servers that require network access should fail gracefully rather than time out.

Battery and compute costs matter. Mobile users are battery-constrained. Servers that do heavy processing on every call — large embedding lookups, complex multi-step retrieval — will create noticeable latency and indirect battery costs. Design for efficiency.

Permission granularity is required. iOS’s privacy model is permission-first. MCP servers registered on iOS must declare explicit permission scopes: what data can they read, what actions can they take? Apple will likely require this in manifest declarations before registration is accepted. If your server currently has broad capabilities, plan for narrower scope declarations for the iOS surface.

Authentication is managed. The system handles session tokens for registered MCP servers, which reduces friction for users but changes the auth flow for server operators. Servers need to support Apple’s token exchange model when iOS acts as the MCP client.

What the Xcode 26.3 MCP Foundation Means

Xcode 26.3 (February 2026) shipped the first Apple MCP implementation: 20 built-in tools covering file system operations, build and test controls, diagnostics, intelligence services, and workspace management. Claude Code and OpenAI Codex connect to Xcode through this server.

iOS 27’s system-wide MCP is built on the same underlying protocol support but extends it from the IDE to the OS. The Xcode implementation proved the protocol works in Apple’s ecosystem. The iOS 27 implementation proves it works at mobile scale.

For builders who built MCP servers that work with Xcode — or that work with Claude Code in Xcode — the path to iOS 27 compatibility is likely straightforward. The protocol is the same. The transport and auth layers will have Apple-specific requirements, but the tool definitions and response formats should port cleanly.

The Scale Shift

Before WWDC 2026, MCP adoption was measured in developers and development contexts. Claude Desktop, Cursor, Xcode, custom agentic apps — the MCP ecosystem was real and growing, but bounded to environments where builders consciously chose to add MCP support.

iOS 27 changes the denominator. Apple has over one billion active iOS devices. macOS adds another 100 million active Macs. Not all of them will be on iOS 27 immediately — the public release is September 2026, and older devices won’t upgrade — but the trajectory is clear: MCP is becoming a mobile-scale protocol.

For the MCP ecosystem, this is the equivalent of a major cloud provider adopting the standard. More users means more demand for MCP-compatible servers. More demand means more ecosystem investment. More ecosystem investment means more servers, which makes MCP more useful for every client — including the non-Apple ones.

What to Do Now

If you operate an existing public MCP server:

  1. Download the iOS 27 developer beta SDK
  2. Watch the “MCP in Apple platforms” WWDC26 session (available now at developer.apple.com/wwdc26)
  3. Review Apple’s capability declaration and permission scope requirements
  4. Benchmark your server’s response time — target under 1 second for Siri compatibility
  5. Add offline failure handling if your server requires network access

If you build iOS or macOS apps:

  1. Watch both “MCP in Apple platforms” and “Introducing Core AI” sessions
  2. Identify which of your app’s capabilities make sense to expose via MCP
  3. Evaluate whether app-bound MCP server registration fits your roadmap before the September 2026 iOS 27 release
  4. If you build enterprise tools: talk to your MDM team about server registration policies now

If you build enterprise AI tools for Apple environments:

  1. Assess which internal tools your organization would benefit from exposing via MDM-registered MCP
  2. Draft a server registration policy alongside your IT/MDM team
  3. Note that the Extensions framework (for Claude/ChatGPT/Gemini as Siri backends) and MCP servers are orthogonal — you may want both

Written June 8, 2026 — the day Apple confirmed system-wide MCP at WWDC 2026. Builder details will continue to emerge from the iOS 27 developer beta and WWDC26 sessions through the week of June 8–12.