Apple answers, backed by Apple sources.
Connect your coding agent to WWDC 2020–2026 sessions, Apple documentation, HIG, Swift Evolution, and App Review guidance. Check real sources before changing your code.
By SMAT Designs. Not affiliated with or endorsed by Apple or OpenAI.
What it is
Connect the hosted service over HTTPS without cloning a repository or building an index. For offline-oriented workflows, you can also run your own local SQLite index over stdio.
Once the MCP is connected and your client calls its tools, inspect the Apple source links and freshness notes before acting on recommendations. A prompt alone does not guarantee tool use.
Key tools
Every tool is read-only. Retrieved content is tagged as evidence, not instructions.
swift_app_auditAudit a Swift/SwiftUI/macOS/iOS app against WWDC sessions, HIG, tutorials, and Swift Evolution.
wwdc_searchHybrid keyword + semantic search across sessions, docs, tutorials, HIG, and evolution proposals.
wwdc_transcript_searchSearch inside session transcripts, not just titles and descriptions.
wwdc_session_deep_linkGenerate a URL with ?time=SECONDS that jumps straight to the chapter in a session.
apple_api_deprecationCheck the deprecation status of an Apple API before your agent uses it.
apple_what_replacedFind the current replacement for a deprecated Apple API.
apple_hig_searchSearch the Human Interface Guidelines for platform behavior rules.
apple_swift_evolution_getPull a Swift Evolution proposal by id (e.g. SE-0428) with status and rationale.
appstore_guidelines_searchSearch the App Store Review Guidelines before you archive a build.
Connect AppDev Atlas
Start with the free hosted service in an MCP client that supports remote Streamable HTTP. No Node.js installation, local index, or Apple account is required for public read-only research.
1. Add the remote MCP URL
In your client's MCP settings, choose a remote HTTP MCP server and paste this endpoint. Connection steps differ by client.
https://wwdc-mcp.smatdesigns.com/mcp
If your client doesn't support remote Streamable HTTP, use the local installation below. The latest MCPB bundle is another option for compatible clients.
2. Ask a specific Apple development question
Use AppDev Atlas to check current Apple guidance for SwiftUI navigation. Show the source links and say what still needs verification.
3. Verify that it actually used the tools
Look for the MCP tool call, a real Apple source URL, and any corpus-freshness caveats. If the agent answers without invoking AppDev Atlas, check the connection and client permissions rather than assuming the research was performed.
Prefer a local index?
Use the stdio server if you want to manage your own index and source updates. This path requires Node.js 22.14+, npm, network access for ingestion, and sufficient time and disk space for the selected corpus. It is not required for hosted use.
1. Clone and build
git clone https://github.com/jabbertones-cloud/wwdc-mcp-server.git cd wwdc-mcp-server npm ci npm run build
2. Ingest the Apple sources you need
npm run ingest:wwdc -- --year 2026
For all supported core sources, run npm run ingest:all. Ingestion can take longer depending on connectivity and corpus size. Keyword search uses local SQLite FTS5; optional semantic reranking uses Hugging Face Transformers/ONNX and may download model files on first use. Ollama is not required.
3. Connect a local MCP client
For example, in Cursor's ~/.cursor/mcp.json:
{
"mcpServers": {
"wwdc": {
"command": "node",
"args": ["/absolute/path/to/wwdc-mcp-server/dist/index.js"]
}
}
}
Replace the path with the actual location of your checkout. For other clients and bundle install details, see the README or support guide.
Know, then ship
Code that compiles is not the finish line. There are two problems, and they are different problems.
AppDev Atlas
Checks what Apple expects — current sessions, docs, HIG, and review guidelines, checked before the code changes.
AiSCent
Gets the release through App Store Connect — screenshots, metadata, localization, TestFlight, and release state. Know what to build; then ship it.