J
jabbertones-cloud/wwdc-mcp-server
★ 1·updated 2026-11-18
View on GitHub ↗Direct link · no redirect page
We have neither an install command nor a public remote endpoint from this repository, so we do not print a config. A made-up one is worse than none. How each client wires MCP up →
- Star count
- 1 ★ · jabbertones-cloud/wwdc-mcp-server · read from the GitHub search API · (checked 2026-11-19 20:00:48)
- Source
- collected from the punkpeye/awesome-mcp-servers list · type: MCP server
- Harvest history
- first seen 2026-11-18 · last seen 2026-11-20 · seen 3× · listed by 3 sources
- Score
- score 300 · 1 ★ · 3 sources · mcp
FAQ (answers come from our records)
Who is it for?
We filed it under these tags: MCP servers. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
jabbertones-cloud/wwdc-mcp-server;first catalogued 2026-11-18;last seen 2026-11-20。There is no official certification or quality rating here — we record sources and dates only.README excerpt (English, untranslated) · Read the full README on GitHub →
# AppDev Atlas — independent Apple-platform research for coding agents
Excerpted from the repository README (abridged)
AppDev Atlas, by SMAT Designs, grounds Codex, Claude, Cursor, VS Code, Windsurf, Zed, and other MCP clients in published Apple-platform material before they change your Swift code. The existing technical package, MCP tools, and hosted endpoint retain their backward-compatible WWDC identifiers. This independent service is not affiliated with or endorsed by Apple or OpenAI.
AppDev Atlas 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.
Support: AppDev Atlas help | GitHub Issues | Report a bug
> 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. In a client that supports remote Streamable HTTP MCP, add https://wwdc-mcp.smatdesigns.com/mcp. No local install, account, or index is needed for public read-only research. If your client is local-only, choose the MCP Registry/MCPB bundle or stdio setup below.
2. Ask: “Use AppDev Atlas to audit this app against current Apple guidance before changing code. Include primary source links and uncertainty.”
3. Check the tool really ran and inspect its cited Apple evidence. A prompt alone does not guarantee MCP invocation, and an audit's seed_context_only result is not approval to edit code.
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. AppDev Atlas 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 swift_app_audit. The promoted trust entry point is wwdc_security_manifest.
## 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 swift_app_audit with the repo's actual feature/API/problem, then follow its evidence into the focused WWDC, HIG, documentation, and API tools.
AppDev Atlas 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.
Support: AppDev Atlas help | GitHub Issues | Report a bug
> 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. In a client that supports remote Streamable HTTP MCP, add https://wwdc-mcp.smatdesigns.com/mcp. No local install, account, or index is needed for public read-only research. If your client is local-only, choose the MCP Registry/MCPB bundle or stdio setup below.
2. Ask: “Use AppDev Atlas to audit this app against current Apple guidance before changing code. Include primary source links and uncertainty.”
3. Check the tool really ran and inspect its cited Apple evidence. A prompt alone does not guarantee MCP invocation, and an audit's seed_context_only result is not approval to edit code.
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. AppDev Atlas 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 swift_app_audit. The promoted trust entry point is wwdc_security_manifest.
## 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 swift_app_audit with the repo's actual feature/API/problem, then follow its evidence into the focused WWDC, HIG, documentation, and API tools.
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/jabbertones-cloud-wwdc-mcp-server/)
- Source
- awesome · https://github.com/jabbertones-cloud/wwdc-mcp-server
- Browse by field
- MCP servers
- Traction
- 1 ★
- Listed by
- 3 independent sources
- added
- today
More MCP servers
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.