WWDC MCP server

WWDC MCP — current Apple developer knowledge for coding agents

<!-- mcp-name: wwdc -->

Ground Codex, Claude, Cursor, VS Code, Windsurf, Zed, and other MCP clients in Apple source material before they change your Swift code.

WWDC MCP indexes WWDC20–WWDC26 sessions, Apple Developer Documentation, tutorials, Human Interface Guidelines, Swift Evolution, The Swift Programming Language, and App Store Review Guidelines into a local SQLite search layer. It exposes 45 read-only MCP tools for search, API history, deprecations, transcripts, source-grounded app audits, and trust metadata.

Unofficial community project. Not affiliated with or endorsed by Apple. Apple content remains subject to Apple's terms and source-site availability.

Pick your path

I just want my coding agent to use Apple knowledge

1. Install/connect WWDC MCP using the MCP Registry/MCPB release or the client config below.
2. Ask: “Use WWDC MCP to audit this app against current Apple guidance before changing code.”
3. Let the agent start with swiftappaudit; you do not need to learn all 45 tools.

I am a power user

Use the focused tools directly for transcripts, API history, HIG, Swift Evolution, App Review, source freshness, and trust metadata. See Agent Guide for recommended tool chains and prompt recipes.

I am an agent working in this repository

Read AGENTS.md first. Client-specific repository instructions are also provided for Cursor and GitHub Copilot.

Why use it?

Coding agents are excellent at writing Swift, but Apple APIs, platform guidance, App Review rules, and WWDC recommendations change quickly. WWDC MCP gives an agent a source-grounded way to answer questions like:

• “What changed in SwiftUI at WWDC26, and which changes matter to this app?”
• “Audit this StoreKit subscription flow against current Apple guidance.”
• “When was this API introduced, is it deprecated, and what replaces it?”
• “Find the exact WWDC chapter that explains this App Intents behavior.”
• “Compare WWDC25 and WWDC26 coverage of Foundation Models.”
• “Check App Store Review Guideline 3.1.1 before I ship.”
• “Audit this macOS app for current SwiftUI, AppKit, concurrency, accessibility, and App Store guidance.”

The promoted entry point for repo-level Apple work is swiftappaudit. The promoted trust entry point is wwdcsecuritymanifest.

Start here: three high-value workflows

You do not need to learn 45 tool names first. Start with the job you are trying to finish:

• Modernize an Apple app: call swiftappaudit with the repo's actual feature/API/problem, then follow its evidence into the focused WWDC, HIG, documentation, and API tools.
• Answer “what changed?”: use wwdcwhatchanged or wwdc_search with a framework/API and a year range, then open the strongest session/transcript evidence.
• Check shipping risk: search appstoreguidelinessearch, API availability/deprecation tools, and wwdcingeststatus before treating a recommendation as current. wwdcingeststatus names the corpus state (stamped / unstamped / empty); an empty state means 0 sessions indexed and warns that a missing corpus volume may be the cause, rather than presenting a healthy empty status.

Shortened. The full README is on GitHub.