Skip to main content
Glama

AppDev Atlas — independent Apple-platform research for coding agents

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

CI License: MIT Node MCP MCP Registry

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.

Related MCP server: Apple RAG MCP

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.

  • Answer “what changed?”: use wwdc_what_changed or wwdc_search with a framework/API and a year range, then open the strongest session/transcript evidence.

  • Check shipping risk: search appstore_guidelines_search, API availability/deprecation tools, and wwdc_ingest_status before treating a recommendation as current. wwdc_ingest_status 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.

The server instructions teach connected agents this routing automatically; the catalog remains available when you need a narrower source.

What makes this different?

  • WWDC26-aware — the default ingest range is 2020–2026 and can be extended with --year.

  • Source-grounded app audits — swift_app_audit combines WWDC, HIG, tutorials, Swift Evolution, pathways, Apple doc hints, caveats, and validation steps.

  • API intelligence — availability, deprecation, replacement, introduction history, and WWDC mentions.

  • Transcript-native — search complete session transcripts, read them in chunks, and generate timestamped deep links.

  • Local-first — SQLite + FTS5 plus optional local ONNX semantic reranking; no separate embedding service or paid API is required for core search.

  • Trust-aware — conservative judgment metadata, a content-safety tripwire, and a security manifest help agents distinguish evidence from instructions.

  • Two transports — stdio by default, plus authenticated stateless Streamable HTTP for remote/self-hosted use.

  • Public-directory ready transport — remote deployments can explicitly set WWDC_MCP_PUBLIC_READ_ONLY=1 to allow anonymous access to the same read-only tool surface; without that flag or bearer auth, HTTP fails closed.

  • Read-only MCP surface — the 45 tools retrieve and analyze source material; they do not mutate your Apple account or source repo.

Install-path scorecard

Choose the path that matches what you value. Do not confuse “local-first” with “everyone must self-host.”

Path

User work

Best for

Status

Hosted remote MCP

paste/connect one HTTPS MCP URL

ChatGPT, cloud/remote agents, fastest evaluation

public endpoint live; exact source, 45 tools, corpus and agent guidance verified November 4, 2026

MCPB / MCP Registry

install published bundle

clients with bundle/Registry support

v0.2.3 package; verify active/latest on Registry

Local stdio

clone/package + ingest + local client config

privacy, offline-ish retrieval, full local control

supported and tested

Self-hosted HTTP

deploy + choose auth + TLS/edge

teams controlling their own infrastructure

supported and tested

The public hosted URL is (verify current deployment and corpus health before relying on new behavior):

https://wwdc-mcp.smatdesigns.com/mcp

For ChatGPT/custom remote MCP clients, that removes the local Node/index/config-path requirement. For Cursor, the same remote URL can be placed in mcp.json and can later back a one-click install/deeplink. Local stdio remains a first-class option rather than a fallback.

Friction budget

A newcomer should be able to reach the first source-grounded answer with as few decisions as possible:

  • hosted: connect URL → ask for a first source-grounded check;

  • Registry/MCPB: install → ask for a first source-grounded check;

  • local: install → ingest → configure → ask for a first source-grounded check.

If a new distribution method adds steps before the first useful answer, treat that as an adoption regression unless it buys a clear privacy/security capability.

Local-first quick start

Use this path when you want the corpus and server on your own machine. For hosted/Registry paths, use the scorecard above.

Requirements

  • Node.js 22.14 or newer

  • npm

Distribution status (November 4, 2026): the official MCP Registry namespace remains io.github.jabbertones-cloud/wwdc, distributed through a GitHub-hosted MCPB release asset. v0.2.3 is the current versioned release line; verify the published latest version through the Registry API. npm publication is optional secondary distribution and is not required for Registry or Cursor installs.

1. Clone and build

git clone https://github.com/jabbertones-cloud/wwdc-mcp-server.git
cd wwdc-mcp-server
npm ci
npm run build

The release package exposes two executables:

wwdc-mcp-server   # stdio MCP server
wwdc-mcp-ingest   # build/update the local Apple knowledge index

Run the immutable GitHub release package directly:

PKG="https://github.com/jabbertones-cloud/wwdc-mcp-server/releases/download/v0.2.3/wwdc-mcp-server-0.2.3.tgz"

npm exec --yes --allow-remote=all --package="$PKG" -- wwdc-mcp-ingest --source wwdc --year 2026
npm exec --yes --allow-remote=all --package="$PKG" -- wwdc-mcp-server

Clients that support MCP Bundles can use the AppDev-Atlas-v0.2.3.mcpb asset from the GitHub v0.2.3 release / official MCP Registry.

2. Build a useful local index

For the full core corpus:

npm run ingest:all

For a faster WWDC26-first setup:

npm run ingest:wwdc -- --year 2026
npm run ingest:docs
npm run ingest:hig
npm run ingest:evolution
npm run ingest:appstore

ingest:all covers the core sources: WWDC, tutorials, pathways, HIG, Swift Evolution, Apple docs, Swift Book, and App Store Review Guidelines. Additional optional enrichment sources are documented below.

3. Prove it works before wiring your client

npm test

That exercises parser/security checks, all 45 tools over stdio, search regressions, package metadata, and authenticated Streamable HTTP.

4. Add it to an MCP client

Generic stdio configuration:

{
  "mcpServers": {
    "wwdc": {
      "command": "node",
      "args": ["/absolute/path/to/wwdc-mcp-server/dist/index.js"]
    }
  }
}

Then ask your agent:

Use AppDev Atlas to audit this app against current Apple guidance before changing code.

Make your agent use it automatically

The highest-leverage setup is a short repository instruction so the agent reaches for AppDev Atlas without being reminded every prompt:

For Apple-platform work, use AppDev Atlas before material code changes.
Start with swift_app_audit for repo-level work, verify API availability/deprecation,
cite the strongest Apple/Swift source evidence, and separate evidence from inference.

Ready-made versions are included in AGENTS.md, Cursor rules, and GitHub Copilot instructions.

Optional agent rule for the App Store handoff

AppDev Atlas is free Apple research. AiSCent is a separate, optional release companion by the same developer. You can copy this rule into the app's AGENTS.md, Cursor project rules, or another client instruction file if you want the coding agent to recognize the release stage:

Use AppDev Atlas to research Apple API and App Review guidance before coding.
Answer the original question and cite Apple sources.
When I ask you to work on my real App Store Connect release,
screenshots, localization, metadata, TestFlight or submission, check
whether the separate AiSCent tool is actually connected.
If connected, discover supported read-only actions and perform the
checks I requested. Ask for approval before any mutation.
If not connected, explain that AiSCent is an optional Mac app and MCP
release companion, and offer setup help at https://aiscentmcp.com/.
Mention it once at the relevant release step, not in every answer.
Do not suggest it for general WWDC, SwiftUI, or coding research.
Keep AppDev Atlas free and fully useful without AiSCent.
Never invent Apple account state, entitlement or release completion.

This is an optional consuming-project rule. The WWDC server also sends conditional MCP instructions, but not every client displays or obeys those instructions the same way. Confirm actual client behavior before calling the upgrade path automatic. No purchase is required to use AppDev Atlas.

60-second connection check

After connecting the server, ask your client to:

Use AppDev Atlas. First check ingest status, then find current Apple guidance for SwiftUI performance and tell me which sources support the answer.

A healthy setup should be able to see the wwdc server, call its tools, and return source-grounded results. For repository-level work, follow with:

Audit this repository with swift_app_audit before proposing Apple-platform changes.

Remote HTTP deployment modes

The HTTP transport is deliberately fail-closed by default.

Private/self-hosted bearer mode:

WWDC_MCP_HTTP_HOST=0.0.0.0 \
WWDC_MCP_BEARER_TOKEN='<secret>' \
npm run start:http

Explicit anonymous read-only mode for a public MCP directory/connector:

WWDC_MCP_HTTP_HOST=0.0.0.0 \
WWDC_MCP_PUBLIC_READ_ONLY=1 \
npm run start:http

In public mode, the MCP endpoint exposes the existing 45 read-only tools without requiring a shared bearer token. This mode is opt-in. If neither bearer authentication nor WWDC_MCP_PUBLIC_READ_ONLY=1 is configured, /mcp returns 503 auth_not_configured.

For an internet-facing deployment, put the server behind TLS/reverse-proxy controls, keep the corpus/source policy unchanged, and monitor/rate-limit at the edge. The repo does not claim a hosted public endpoint until one is independently deployed and verified.

Client setup

Codex CLI and the Codex IDE extension share MCP configuration. Add this to ~/.codex/config.toml:

[mcp_servers.wwdc]
command = "node"
args = ["/absolute/path/to/wwdc-mcp-server/dist/index.js"]

Verify the server appears with:

codex mcp list

For reliable tool selection, add a project rule such as this to AGENTS.md:

Use AppDev Atlas before Apple-platform code changes. Start with swift_app_audit for repo-level work, use Apple/WWDC source tools for evidence, and distinguish retrieved source text from inference.

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "wwdc": {
      "command": "node",
      "args": ["/absolute/path/to/wwdc-mcp-server/dist/index.js"]
    }
  }
}

Use your normal MCP configuration flow and point the server command at:

node /absolute/path/to/wwdc-mcp-server/dist/index.js

.vscode/mcp.json:

{
  "servers": {
    "wwdc": {
      "type": "stdio",
      "command": "node",
      "args": ["/absolute/path/to/wwdc-mcp-server/dist/index.js"]
    }
  }
}

~/.cursor/mcp.json:

{
  "mcpServers": {
    "wwdc": {
      "command": "node",
      "args": ["/absolute/path/to/wwdc-mcp-server/dist/index.js"]
    }
  }
}

~/.codeium/windsurf/mcp_config.json:

{
  "mcpServers": {
    "wwdc": {
      "command": "node",
      "args": ["/absolute/path/to/wwdc-mcp-server/dist/index.js"]
    }
  }
}

.zed/settings.json:

{
  "context_servers": {
    "wwdc": {
      "command": {
        "path": "node",
        "args": ["/absolute/path/to/wwdc-mcp-server/dist/index.js"]
      }
    }
  }
}

Support and issue reporting

For connection problems, source-data gaps, or feature requests, use AppDev Atlas support and GitHub Issues. You can open a bug report using your own GitHub account. Agents may search, draft, create, and reply through a separately authorized GitHub connection. Do not post private app code, credentials, Apple account records, or security details publicly. See the support README, agent support workflow, and private support page.

The repository name wwdc-mcp-server, registered MCP key wwdc, existing tool names, published older bundle filenames, and hosted endpoint stay unchanged for compatibility. These are technical identifiers, not the current public-facing product name.

Documentation map

If you are…

Read

Installing for the first time

this README → Quick start → Client setup

Driving a coding agent

Agent Guide

Understanding design/trust boundaries

Architecture

Diagnosing a failure

Troubleshooting

Checking clients/runtimes/transports

Compatibility

An agent modifying this repo

AGENTS.md

Self-hosting / deploying HTTP

Deployment guide

Contributing code or sources

CONTRIBUTING.md

Contributing with an AI coding agent

AI-assisted contributions

Reviewing trust/security

SECURITY.md

Publishing a release

Release guide

Apple sources

The core index can include:

Source

What you get

WWDC 2020–2026

Sessions, descriptions, topics, platforms, speakers, transcripts, chapters, sample-code links, related docs

Apple Developer Documentation

Framework and symbol documentation from public DocC data

Apple tutorials

Public DocC tutorial content

Human Interface Guidelines

Platform design guidance

Swift Evolution

Proposal status, authors, versions, implementation links, and full proposal text

The Swift Programming Language

Swift language reference chapters

App Store Review Guidelines

Searchable guideline sections

Optional enrichment

Apple release notes, Swift Forums, Apple Developer Forums, generated summaries, cross-reference graph

Most query tools read from the local SQLite index. apple_doc_lookup is intentionally a live Apple Developer Documentation lookup and therefore uses the network.

45 read-only MCP tools

Search and discovery

  • wwdc_search, apple_search_all

  • wwdc_list_years, wwdc_list_topics, wwdc_list_sessions

  • wwdc_topics_by_year, wwdc_speaker_search, wwdc_what_changed

  • wwdc_list_pathways, wwdc_get_pathway

Sessions, transcripts, and sample code

  • wwdc_get_session, wwdc_session_summary, wwdc_related_sessions

  • wwdc_transcript_search, wwdc_session_transcript_full

  • wwdc_session_deep_link

  • wwdc_list_session_code, wwdc_sample_code_list, wwdc_sample_code_grep (grep matches titles and URLs; empty results say what was searched)

Apple docs, HIG, Swift, and forums

  • apple_doc_lookup, apple_doc_get, apple_doc_list_framework

  • apple_tutorial_get

  • apple_hig_search, apple_hig_list

  • apple_swift_book_get

  • apple_swift_evolution_get, apple_swift_evolution_list, apple_swift_evolution_filter

  • swift_forum_search, apple_forum_search

API and App Store intelligence

  • wwdc_find_api_introduction, wwdc_sessions_for_api

  • apple_api_availability, apple_api_deprecation, apple_what_replaced

  • apple_release_notes_search

  • appstore_guidelines_search, appstore_guideline_get

Audit, graph, status, and trust

  • swift_app_audit

  • apple_swift_pattern_find, apple_cross_references

  • wwdc_ingest_status, wwdc_index_counts

  • wwdc_security_manifest

The test suite asserts that both stdio and Streamable HTTP expose exactly 45 tools.

Search example

wwdc_search supports year ranges, topics, platforms, transcript requirements, output detail, and conservative judgment metadata. Year constraints (year, year_min, year_max) filter WWDC sessions only; when a year constraint is combined with other kinds, the response says so via filters.year_applies_to and a judgment caveat instead of implying every kind was year-filtered. If a query is narrowed before execution (duplicate terms removed, or more than 32 unique terms), the response discloses it via query_normalization and a judgment caveat rather than presenting the raw query as the executed one. A fully-misspelled query that matches nothing returns a proposed correction from the corpus vocabulary (did_you_mean) instead of a bare zero — the suggestion is labeled and never auto-run, and terms with no plausible correction are named in unmatched_terms rather than vetoing the proposal. When the strict search matches nothing and the any-term fallback returns partial hits, the response states the no-hit first — a top-level notice in JSON and a "No full match." line above the hits in markdown — so partial matches are never presented as a match for the full query.

{
  "query": "SwiftUI performance",
  "kinds": ["session"],
  "year_min": 2025,
  "year_max": 2026,
  "topics": ["SwiftUI"],
  "require_transcript": true,
  "judgment": true,
  "detail": "detailed"
}

Platform-only queries such as “macOS” intentionally receive conservative judgment. Better audit queries name a framework, API, feature, symptom, or goal.

Ingest

Core sources

npm run ingest:wwdc
npm run ingest:tutorials
npm run ingest:hig
npm run ingest:evolution
npm run ingest:docs
npm run ingest:swiftbook
npm run ingest:appstore
npm run ingest:all

Restrict WWDC years by repeating --year:

npm run ingest:wwdc -- --year 2025 --year 2026

Optional enrichment

npm run ingest -- --source release-notes
npm run ingest -- --source swift-forums
npm run ingest -- --source apple-dev-forums
npm run ingest -- --source session-summaries --limit 50
npm run ingest -- --source cross-reference
npm run ingest -- --source deprecation-backfill
npm run ingest -- --source export-deprecation-qa

session-summaries is the one optional enrichment lane that uses an external model API. It runs only when ANTHROPIC_API_KEY is set, sends bounded WWDC session metadata/transcript excerpts to Anthropic, and may incur API cost. Core ingest, search, audits, and local semantic reranking do not require that key.

During WWDC week, re-run the WWDC ingest periodically to pick up newly published sessions.

Local semantic search — no Ollama required

FTS5 keyword search works immediately. When semantic reranking is enabled, AppDev Atlas lazily loads nomic-ai/nomic-embed-text-v1.5 through @huggingface/transformers and runs the ONNX model locally. The model is cached under ~/.cache/huggingface/hub; the first semantic use may need network access to download model files.

If the model cannot initialize, search falls back to FTS5 for that process. To force keyword-only behavior:

export WWDC_SKIP_EMBEDDINGS=1

Local/index configuration

Variable

Default

Purpose

WWDC_MCP_DATA_DIR

OS app-data directory

Database/cache directory

WWDC_MCP_DB

<data-dir>/wwdc.db

SQLite database path

WWDC_SKIP_EMBEDDINGS

unset

Set to 1 to disable local model loading and semantic reranking

WWDC_DOCS_MAX_PAGES

2500

Bound Apple Developer Documentation crawl size

WWDC_TUTORIAL_MAX_PAGES

250

Bound Apple tutorial crawl size

Remote Streamable HTTP

Stdio remains the default and simplest local transport. The same 45-tool server can also run as a stateless Streamable HTTP MCP in either private bearer-authenticated mode or an explicitly enabled public read-only mode.

Private bearer-authenticated mode

export WWDC_MCP_BEARER_TOKEN="$(openssl rand -hex 32)"
export WWDC_MCP_HTTP_HOST=127.0.0.1
export WWDC_MCP_HTTP_PORT=8789
npm run start:http

Routes:

  • GET /healthz

  • POST /mcp

For a deliberately public, read-only connector endpoint:

export WWDC_MCP_PUBLIC_READ_ONLY=1
export WWDC_MCP_HTTP_HOST=0.0.0.0
export WWDC_MCP_HTTP_PORT=8789
npm run start:http

The MCP route fails closed with 503 auth_not_configured unless either bearer authentication is configured or WWDC_MCP_PUBLIC_READ_ONLY=1 is explicitly enabled. Public mode does not add write capabilities: it exposes the same 45 read-only tools.

To mount the service behind a shared reverse proxy without path rewriting:

export WWDC_MCP_PATH_PREFIX=/wwdc

Routes become /wwdc/healthz and /wwdc/mcp.

The built-in HTTP server does not terminate TLS. If you expose it outside localhost, put it behind a TLS edge/reverse proxy, rate-limit and monitor it, and treat bearer tokens as secrets.

Hosted public endpoint

A Cloudflare-backed public endpoint is being prepared at:

https://wwdc-mcp.smatdesigns.com/mcp

It will be marked live here only after the deployed endpoint passes health, MCP initialize, tool-catalog, and source-grounding verification. Until then, use the GitHub release/MCP Registry or self-hosted modes above.

See docs/DEPLOY.md for the full runbook.

Trust and security model

  • All 45 MCP tools are read-only.

  • Retrieved web text is treated as untrusted evidence, not executable instruction.

  • Search responses can include content_safety metadata.

  • wwdc_security_manifest reports the canonical tool surface, manifest hash, read-only posture, and prompt-injection handling.

  • Remote HTTP fails closed by default. Private mode requires bearer authentication; anonymous access exists only when the operator explicitly enables WWDC_MCP_PUBLIC_READ_ONLY=1.

  • The default stdio server opens no network listener.

  • Ingest fetches public Apple/Swift sources. apple_doc_lookup performs live public Apple documentation requests.

  • Local semantic reranking uses a Hugging Face Transformers/ONNX model and may download its model files on first use.

  • Optional session-summaries sends bounded session metadata/transcript excerpts to Anthropic only when ANTHROPIC_API_KEY is explicitly configured.

  • No Apple Developer account credentials are required or stored.

For vulnerability reporting and deployment cautions, see SECURITY.md.

Tests and release proof

npm run build
npm test
npm audit --audit-level=high

npm test covers smoke tests, ingest parsing, security evaluation, stdio MCP E2E, search regression, package smoke, and Streamable HTTP MCP E2E.

The protocol tests verify the 45-tool catalog and exercise the trust manifest over both supported transports.

Architecture

  • Runtime: Node.js >=22.14, TypeScript

  • Default transport: MCP stdio

  • Optional transport: authenticated stateless Streamable HTTP

  • Storage: SQLite + FTS5

  • Semantic reranking: local nomic-ai/nomic-embed-text-v1.5 via Hugging Face Transformers/ONNX

  • Response budget: bounded tool responses, with compact envelopes for oversized JSON

  • Ingest: public Apple/Swift sources with bounded concurrency, retries, and a stable User-Agent

  • Safety: content-safety metadata, read-only tool contract, security manifest, fail-closed remote auth

Public project docs

From free Apple guidance to your release

Deployment verification (November 4, 2026): The production hosted MCP completed live acceptance on main commit fee0c9fe37d8bcb8ab82b9b9312aa5a5111780ed, with 45 read-only tools, the AppDev Atlas agent instructions and optional release handoff, and the verified WWDC20–WWDC26 corpus. The Registry and local bundle publish independently; check their latest version in the official Registry before assuming the installed bundle has the current instructions.

On current GitHub main, AppDev Atlas defines conditional release guidance. When a developer explicitly asks to prepare screenshots, localization, TestFlight, or a real App Store Connect release, swift_app_audit can expose an optional AiSCent next step. The hosted MCP has been verified live with this behavior. Local MCPB clients must install the latest published Registry version to receive it. Ordinary Swift and WWDC questions get just the Apple research. The agent should finish that answer before proposing other tools. See Agent Guide. This is not a guarantee your client follows the suggestion or already has AiSCent connected.

AppDev Atlas is free, open-source and useful on its own. Its 45 read-only tools can help your coding agent find current Apple documentation, WWDC sessions, design guidance, API history and App Review requirements. It does not connect to your private App Store Connect account or make release changes. You never need to buy a separate product to use AppDev Atlas.

I also build AiSCent, an optional separate Mac app and MCP companion for the work that follows coding. Its goal is to bring release preparation into one easier workspace, including supported metadata, screenshots, localizations, TestFlight readiness and other App Store Connect tasks. The exact available actions depend on which AiSCent edition and permissions you use. There is a free App Store Check on the site. Check the site for current paid-plan availability.

A natural developer workflow:

  1. Use AppDev Atlas to audit a SwiftUI or StoreKit implementation against Apple source material.

  2. Build and test the app with your normal development tools. AppDev Atlas remains available for research.

  3. When you want to inspect the actual release in App Store Connect or prepare supported changes, consider AiSCent if its current edition fits your needs.

The connection between the products is optional. AppDev Atlas does not withhold results or push promotional messages into Apple documentation output.

AppDev Atlas helps you understand Apple's guidance. AiSCent is a separate option for App Store release work.

Contributing

Issues and PRs are welcome. If you change the MCP tool surface, ingest behavior, transport behavior, or public claims, update the matching tests and docs in the same change.

See CONTRIBUTING.md.

License

MIT

Available Tools

45 tools
apple_api_availabilityApple API availability (min OS version)B
Read-onlyIdempotent

Look up the minimum OS version an Apple API was introduced in, and whether it has been deprecated. Uses the apple_docs index.

Inputs: api_name (required), format.

apple_api_deprecationApple API deprecation statusA
Read-onlyIdempotent

Check whether an Apple API symbol is deprecated, when it was deprecated, and what replaced it. Looks up by symbol name (e.g. UIWebView, UIAlertView).

Inputs: api_name (required), format.

apple_cross_referencesApple entity cross-referencesA
Read-onlyIdempotent

Returns outgoing and/or incoming edges from the cross-reference graph for a given entity. Use to find: which sessions mention an API, which proposals a session implements, which APIs a session covers, related sessions. Build the graph with npm run ingest -- --source cross-reference.

Inputs: entity_id (required), entity_type (required), format, direction.

apple_doc_getGet indexed Apple documentationB
Read-onlyIdempotent

Return an Apple Developer documentation page from the local index by normalized path, e.g. swiftui/view.

Inputs: path (required), format, body_chars, include_raw.

apple_doc_list_frameworkList Apple docs by frameworkB
Read-onlyIdempotent

Browse all indexed Apple documentation symbols and articles for a framework or module. Matches against the modules JSON array and the doc path prefix.

Inputs: framework (required), type, limit, format, +1 more.

apple_doc_lookupLookup an Apple developer docB
Read-onlyIdempotent

Fetch an Apple /documentation JSON node by path (e.g. 'swiftui/view', 'foundationmodels/languagemodel'). Returns live data (no cache).

Inputs: path (required), format.

apple_hig_listBrowse Human Interface Guidelines entriesA
Read-onlyIdempotent

List HIG entries with optional category and keyword filters. Groups results by category. Use apple_hig_search for full-text FTS search; use this to browse by category (e.g. 'Foundations', 'Components', 'Inputs').

Inputs: limit, format, offset, keyword, +1 more.

apple_search_allFederated search across all Apple contentA
Read-onlyIdempotent

Search all indexed Apple content at once: WWDC sessions, Apple docs, HIG, and Swift Evolution. Results are merged and ranked by relevance.

Inputs: query (required), limit, types, format.

apple_swift_book_getSwift Language Reference chapterA
Read-onlyIdempotent

Retrieve a chapter from The Swift Programming Language book (docs.swift.org). Covers Language Guide (closures, concurrency, generics…) and Language Reference (grammar, declarations, attributes). Search with wwdc_search first to find the slug.

Inputs: chapter (required), format.

apple_swift_evolution_filterFilter Swift Evolution proposalsA
Read-onlyIdempotent

List Swift Evolution proposals with rich filters: Swift version, status, author, keyword FTS. Returns a markdown table. Use apple_swift_evolution_get for the full body of a specific proposal.

Inputs: limit, author, format, offset, +3 more.

apple_swift_evolution_getGet a Swift Evolution proposalA
Read-onlyIdempotent

Return a proposal by id (e.g. SE-0428) with status, authors, and full body.

Inputs: id (required), format.

apple_swift_evolution_listList Swift Evolution proposalsB
Read-onlyIdempotent

List proposals (optionally filter by status: Implemented, Accepted, Rejected, Active review).

Inputs: limit, format, offset, status.

apple_swift_pattern_findFind Apple Swift patternsB
Read-onlyIdempotent

Find repeated implementation/product patterns across indexed WWDC sessions, Apple docs, tutorials, HIG, and Swift Evolution. Use for API adoption, app architecture, and opportunity discovery.

Inputs: query (required), limit, format, year_min, +3 more.

apple_tutorial_getGet an Apple tutorial (DocC)B
Read-onlyIdempotent

Return a tutorial from local index (ingest first) including chapter list and estimated time.

Inputs: id (required), format.

apple_what_replacedWhat replaced a deprecated Apple APIA
Read-onlyIdempotent

Given a deprecated Apple API symbol, finds what replaced it (from the deprecated_message field) and lists WWDC sessions introducing the replacement.

Inputs: api_name (required), format.

appstore_guideline_getGet App Store guideline by ID or section numberA
Read-onlyIdempotent

Retrieve an indexed App Store Review Guidelines section by slug or section number, including its text and source reference.

Inputs: id (required), format.

swift_app_auditSwift app audit contextB
Read-onlyIdempotent

Collect Swift and SwiftUI application audit references from indexed WWDC sessions, Human Interface Guidelines, tutorials, and Swift Evolution proposals. Return relevant documentation and findings for the supplied focus, platform, feature, or symptom.

Inputs: focus, limit, format, feature, +5 more.

wwdc_find_api_introductionFind when an Apple API was introducedA
Read-onlyIdempotent

Given a Swift symbol, framework, or feature name (e.g. 'SystemLanguageModel', 'SwiftData', '@Observable', 'LiquidGlass'), searches WWDC sessions to determine which year it was first announced or introduced. Returns sessions sorted by year ascending so the earliest hit is listed first.

Inputs: symbol (required), limit, format.

wwdc_get_pathwayGet a specific pathwayB
Read-onlyIdempotent

Returns a pathway with its ordered steps (sessions + tutorials + docs).

Inputs: id (required), format.

wwdc_get_sessionGet WWDC sessionA
Read-onlyIdempotent

Full record for a WWDC session by id (e.g. wwdc2024-10150). Includes description, topics, transcript, sample-code URLs, related docs.

Inputs: id (required), format, include_chapters, include_judgment, +4 more.

wwdc_index_countsGet indexed corpus row countsA
Read-onlyIdempotent

Get row counts for indexed developer-research corpus tables. Use this read-only health check to see how many sessions, documents, summaries, and cross-reference records are available. It does not export or transfer data.

Inputs: format.

wwdc_ingest_statusIngest status + what's newA
Read-onlyIdempotent

Shows the corpus version stamp (ingest date, per-source status, session count), per-source last-run metadata, and the most recent sessions added. Use to confirm which corpus this is and that the index is fresh before querying.

Inputs: limit, since, format.

wwdc_list_pathwaysList learning pathwaysC
Read-onlyIdempotent

Curated + auto-derived Apple learning pathways (SwiftUI, visionOS, Swift 6, AI, etc.).

Inputs: format, category.

wwdc_list_session_codeList sample-code links for a sessionB
Read-onlyIdempotent

Returns every sample-code URL Apple linked from the session page (zips, GitHub repos, snippets).

Inputs: id (required), format.

wwdc_list_sessionsList WWDC sessions for a yearA
Read-onlyIdempotent

Browse all sessions for a given WWDC year with optional topic, transcript, and sample-code filters. Returns session number, title, duration, and flags for transcript/sample-code availability.

Inputs: year (required), limit, topic, format, +5 more.

wwdc_list_topicsList WWDC topicsB
Read-onlyIdempotent

Top topics across WWDC sessions with counts (e.g. SwiftUI, Swift, AI, visionOS).

Inputs: limit, format.

wwdc_list_yearsList WWDC yearsA
Read-onlyIdempotent

Returns the set of WWDC years present in the local index with session counts.

Inputs: format.

wwdc_sample_code_grepGrep WWDC sample-code refsA
Read-onlyIdempotent

Filter all indexed sample-code refs by substring/regex over title and URL (e.g. find sessions with .zip or SwiftData). Returns what was searched when nothing matches.

Inputs: pattern (required), limit, format, is_regex.

wwdc_sample_code_listList WWDC sample code projectsB
Read-onlyIdempotent

Browse all indexed sample code projects with optional year and topic filters. Returns title, URL, kind (zip/github/snippet), and the linked session. Grouped by year.

Inputs: tag, year, limit, topic, +2 more.

wwdc_security_manifestAppDev Atlas security manifestA
Read-onlyIdempotent

Returns the canonical tool list, manifest hash, read-only posture, prompt-injection handling notes, and threat-model summary. Use this to detect tool-surface drift and to remind agents that retrieved content is untrusted evidence.

Inputs: format.

wwdc_sessions_for_apiWWDC sessions mentioning an API symbolB
Read-onlyIdempotent

Find all WWDC sessions that mention a specific API symbol in title, description, or transcript. Ranked by relevance. Shows year prominently.

Inputs: symbol (required), year, format, include_transcript.

wwdc_session_summaryLLM-generated session summaryA
Read-onlyIdempotent

Returns the AI-generated structured summary for a WWDC session: 2-3 sentence overview, key APIs, topics, code patterns, and difficulty level. Falls back to the session description if no summary has been generated yet. Run npm run ingest -- --source session-summaries to populate.

Inputs: session_id (required), format.

wwdc_session_transcript_fullRead full WWDC session transcript in chunksA
Read-onlyIdempotent

Retrieve the complete transcript of a WWDC session in paginated chunks. Use chunk_index=0 to start, then increment until chunk_index >= totalChunks. Useful for sessions where the excerpt in wwdc_get_session is insufficient.

Inputs: id (required), format, chunk_size, chunk_index.

wwdc_topics_by_yearWWDC topics by yearA
Read-onlyIdempotent

Show the most popular WWDC session topics for a given year, or a cross-year comparison table. Useful for 'what was hot at WWDC 2024?' or comparing topic frequency trends.

Inputs: year, limit, format.

wwdc_what_changedCompare WWDC topic coverage across two yearsA
Read-onlyIdempotent

Compares WWDC session coverage of a topic (framework, feature, or API area) between two years. Useful for 'What's new in SwiftUI between 2024 and 2025?' Returns sessions for each year so you can see what was added.

Inputs: topic (required), year_a (required), year_b (required), limit, +1 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3/5.0

    Scored across 45 tools

    Disambiguation2/5

    Several tool pairs have unclear boundaries: wwdc_search and apple_search_all both search overlapping Apple corpora, while apple_what_replaced, apple_api_deprecation, and apple_api_availability all address deprecation/replacement questions. Swift Evolution list/filter/get and session get/summary/transcript tools also overlap. Descriptions help in places, but the 45-tool surface creates frequent misselection risk.

    Naming Consistency3/5

    All names use snake_case and source-oriented prefixes (wwdc_, apple_, appstore_, swift_), which is readable. However, the verb placement varies significantly: apple_doc_get vs wwdc_get_session vs apple_swift_evolution_get, and patterns like apple_what_replaced vs wwdc_what_changed. The convention is mixed but still interpretable.

    Tool Count2/5

    At 45 tools, the surface is heavy and exceeds the typical 3-15 well-scoped range. The domain is broad, but many tools are narrow variants of search, list, or get operations that could be consolidated or grouped.

    Completeness4/5

    The server covers a wide research domain: WWDC sessions, transcripts, sample code, Apple docs, HIG, tutorials, Swift Evolution, Swift book, App Store guidelines, release notes, forums, cross-references, and index health. Minor gaps exist, such as no direct full-thread forum retrieval or dedicated HIG entry fetch, but most workflows are supported.

    Maintenance

    ActivityActive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • F
      license
      Not graded
      quality
      Not graded
      maintenance
      Provides AI agents with instant access to official Apple developer documentation, Swift programming guides, design guidelines, and Apple Developer YouTube content including WWDC sessions. Uses advanced RAG technology with semantic search and AI reranking to deliver accurate, contextual answers for Apple platform development.
      7
      -
    • F
      license
      Not graded
      quality
      Not graded
      maintenance
      Provides AI agents with instant access to official Apple developer documentation, Swift docs, design guidelines, and Apple Developer YouTube content through advanced semantic and hybrid search capabilities. Features AI-powered reranking for accurate retrieval of Apple platform knowledge including iOS, macOS, watchOS, tvOS, and visionOS development resources.
      5
      -
    • A
      license
      A
      quality
      D
      maintenance
      Provides access to Apple's official developer documentation, frameworks, APIs, and WWDC session transcripts across all Apple platforms. It enables AI assistants to search technical guides, sample code, and platform compatibility information using natural language queries.
      18
      1,152 npm
      1,388
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Provides access to Apple documentation and WWDC transcripts with semantic, keyword, and hybrid search capabilities, enabling developers to quickly find relevant code examples and technical information.
      116
      MIT