Skip to main content
mcpSource-backed

Cupertino MCP Server

Local Apple documentation CLI and MCP server that gives Claude searchable offline access to Apple Developer Documentation, Swift Evolution proposals, Human Interface Guidelines, sample code, Swift.org pages, the Swift Book, and Swift package metadata.

by mihaelamj · submitted by oktofeesh1·added 2026-06-06·
Review first review before installing

Open the source and read safety notes before installing.

Citation facts

Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.

Source URLs
https://github.com/mihaelamj/cupertino/blob/main/README.md, https://github.com/mihaelamj/cupertino
Brand
Cupertino
Brand domain
github.com
Safety notes
Cupertino is an independent third-party project, not an official Apple project., The setup flow downloads a large local documentation bundle; review available disk space and cache locations before installing on managed machines., Self-building or refreshing the corpus can crawl Apple documentation and related public sources; respect Apple site terms and internal network policies., Codex users should pass `serve --no-reap` because upstream documents Codex process spawning behavior that can otherwise close the transport during tool calls., Documentation answers can be stale or incomplete after Apple platform releases, so verify compatibility-sensitive API, beta, and deprecation guidance against live Apple documentation before shipping code.
Privacy notes
Cupertino serves local public documentation over stdio, but prompts and tool results can still expose app architecture, API choices, platform targets, package interests, and sample-code queries to the MCP client, model provider, and logs., The server writes operational output to stderr and uses structured logging; avoid including proprietary source code, unreleased product names, customer data, private bundle identifiers, or internal roadmap details in documentation prompts., Local databases and bundle paths may reveal the developer's Apple-platform focus or package interests to anyone with access to the machine or MCP client logs.
Author
mihaelamj
Submitted by
oktofeesh1
Claim status
unclaimed
Last verified
2026-06-06

Decision playbook

Review trust signals before you adopt

Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.

Compare context
Selected

0

Current score

63

Baseline

Delta

No baseline selected

No major trust-signal divergence detected in the current selection.

Source and provenance checks

Needs review

Confirm ownership and provenance before trusting install instructions.

  • Source link availableRequired

    Open the canonical repository and verify ownership.

    Done
  • Source provenance statusRequired

    Marked as source-backed.

    Done
  • Metadata reviewed

    No reviewed flag detected in metadata.

    Pending

Safety and privacy checks

Complete

Validate risk disclosures before installation or API wiring.

  • Safety notes presentRequired

    Review the listed safety guidance before running commands.

    Done
  • Privacy notes presentRequired

    Review data handling notes before connecting accounts or secrets.

    Done
  • Trust level risk gateRequired

    Trust level does not block evaluation.

    Done

Package and install checks

Needs review

Check package metadata and artifact integrity signals.

  • Install payload available

    Install or copy payload is available for review.

    Done
  • Package verification flag

    No package verification flag provided.

    Pending
  • Checksum metadata

    No checksum provided for downloaded artifact.

    Pending

Compare-driven decision checks

Needs review

Use compare context to validate trade-offs before adoption.

  • Compare tray has multiple entries

    Add at least one more entry to compare trust differences.

    Pending
  • Baseline comparison available

    No baseline peer selected yet.

    Pending
  • Diverging trust signals identified

    No major trust-signal divergence found.

    Pending

Setup at a glance

CLI install

Copy-ready — paste the snippet to get started.

20 minutes

Adoption plan

Balanced adoption plan

Current risk score 24/100. Use staged verification before broader rollout.

Risk 24

Pre-adoption checks

Validate source and review signals before any execution.

  • Confirm source provenanceRequired

    Source URL/provenance metadata is present.

    Done
  • Confirm metadata review state

    No review metadata found; increase manual validation.

    Pending
  • Verify install payload

    Install/config payload exists and can be inspected.

    Done

Security checks

Confirm safety, privacy, and package integrity signals.

  • Review safety notesRequired

    Safety notes are present.

    Done
  • Review privacy notesRequired

    Privacy notes are present.

    Done
  • Verify package integrity metadata

    No package verification/checksum metadata.

    Pending

Rollout

Adopt in controlled steps based on the selected plan.

  • Run in isolated sandbox firstRequired

    Use a constrained sandbox and observe behavior across multiple tasks.

    Pending
  • Roll out graduallyRequired

    Roll out to a small cohort before wider usage.

    Pending
  • Set monitoring and fallback

    Define rollback path and monitor errors after adoption.

    Pending

Evidence readiness

Evidence readiness matrix · balanced

Missing required evidence: Metadata review. Risk score 31.

Risk 31

Source provenance

Present

Source repository/provenance is listed.

Required in this preset

Metadata review

Missing

Review metadata is missing.

Required in this preset

Safety notes

Present

Safety notes are present.

Required in this preset

Privacy notes

Present

Privacy notes are present.

Optional in this preset

Package integrity

Missing

Package integrity metadata is missing.

Optional in this preset

Install payload

Present

Install payload is available.

Required in this preset

Required gaps: Metadata review

Decision timeline

Decision timeline · balanced

Blocking gaps: Check metadata review status. Risk 28.

Risk 28

triage

Confirm source provenanceRequired

Source/provenance metadata is available.

Done

triage

Check metadata review statusRequired

Review metadata is missing.

Pending

verify

Review safety notesRequired

Safety notes are available.

Done

verify

Review privacy notes

Privacy notes are available.

Done

verify

Validate package integrity metadata

Package integrity metadata is missing.

Pending

rollout

Verify install payload and commandsRequired

Install payload is available.

Done

Blockers: Check metadata review status

Prerequisite readiness

Prerequisite readiness

5 prerequisites to line up before setup.

0/5 ready
Install & runtime1Network & hosting3General120 minutes

Safety & privacy surface

Safety & privacy surface

5 safety and 3 privacy notes across 6 risk areas. Review closely: network access, third-party handling.

6 areas
  • SafetyThird-party handlingCupertino is an independent third-party project, not an official Apple project.
  • SafetyNetwork accessThe setup flow downloads a large local documentation bundle; review available disk space and cache locations before installing on managed machines.
  • SafetyNetwork accessSelf-building or refreshing the corpus can crawl Apple documentation and related public sources; respect Apple site terms and internal network policies.
  • SafetyExecution & processesCodex users should pass `serve --no-reap` because upstream documents Codex process spawning behavior that can otherwise close the transport during tool calls.
  • SafetyGeneralDocumentation answers can be stale or incomplete after Apple platform releases, so verify compatibility-sensitive API, beta, and deprecation guidance against live Apple documentation before shipping code.
  • PrivacyThird-party handlingCupertino serves local public documentation over stdio, but prompts and tool results can still expose app architecture, API choices, platform targets, package interests, and sample-code queries to the MCP client, model provider, and logs.
  • PrivacyData retentionThe server writes operational output to stderr and uses structured logging; avoid including proprietary source code, unreleased product names, customer data, private bundle identifiers, or internal roadmap details in documentation prompts.
  • PrivacyLocal filesLocal databases and bundle paths may reveal the developer's Apple-platform focus or package interests to anyone with access to the machine or MCP client logs.

Safety notes

  • Cupertino is an independent third-party project, not an official Apple project.
  • The setup flow downloads a large local documentation bundle; review available disk space and cache locations before installing on managed machines.
  • Self-building or refreshing the corpus can crawl Apple documentation and related public sources; respect Apple site terms and internal network policies.
  • Codex users should pass `serve --no-reap` because upstream documents Codex process spawning behavior that can otherwise close the transport during tool calls.
  • Documentation answers can be stale or incomplete after Apple platform releases, so verify compatibility-sensitive API, beta, and deprecation guidance against live Apple documentation before shipping code.

Privacy notes

  • Cupertino serves local public documentation over stdio, but prompts and tool results can still expose app architecture, API choices, platform targets, package interests, and sample-code queries to the MCP client, model provider, and logs.
  • The server writes operational output to stderr and uses structured logging; avoid including proprietary source code, unreleased product names, customer data, private bundle identifiers, or internal roadmap details in documentation prompts.
  • Local databases and bundle paths may reveal the developer's Apple-platform focus or package interests to anyone with access to the machine or MCP client logs.

Prerequisites

  • macOS with Cupertino's current upstream-supported binary or build toolchain.
  • Homebrew or a manual install path for the Cupertino binary.
  • Approximately 4.2 GB of free disk space for the full pre-built documentation bundle.
  • Network access for the initial database download, or time to crawl and index the documentation sources yourself.
  • An MCP client that supports stdio servers, such as Claude Code, Claude Desktop, Codex, Cursor, VS Code, Zed, Windsurf, or opencode.

Schema details

Install type
cli
Troubleshooting
No
Source repository stats
Scope
Source repo
Collection metadata
Estimated setup
20 minutes
Difficulty
intermediate
Full copyable content
{
  "mcpServers": {
    "cupertino": {
      "command": "/opt/homebrew/bin/cupertino",
      "args": ["serve"]
    }
  }
}

About this resource

Content

Cupertino is a Swift-based Apple documentation CLI and MCP server. It gives Claude and other MCP clients a local searchable index for Apple Developer Documentation, Swift.org pages, Swift Evolution proposals, Human Interface Guidelines, Apple Archive guides, the Swift Book, Swift package metadata, and Apple sample-code files.

Use it when an Apple-platform project needs fast API lookup, framework search, sample-code discovery, HIG checks, or Swift language context without manually opening multiple documentation sites. The same local index powers terminal commands such as cupertino search and the stdio MCP server launched by cupertino serve.

Source Review

These sources were reviewed on 2026-06-06. Prefer the live repository, README, license, Swift package manifest, MCP client setup guide, serve command documentation, search tool documentation, CLI serve implementation, MCP server implementation, and stdio transport implementation for current install and behavior details.

Features

  • Search Apple Developer Documentation, Swift Evolution, Swift.org, the Swift Book, HIG pages, Apple Archive guides, Swift package metadata, and Apple sample-code files.
  • Read documentation through MCP resources such as apple-docs://, swift-evolution://, and hig:// URIs.
  • Run unified full-text search through the search MCP tool with source, framework, language, archive, limit, and platform-version filters.
  • List frameworks and read selected documents from the local index.
  • Explore sample projects with list_samples, read_sample, and read_sample_file.
  • Search extracted Swift symbols, property wrappers, concurrency APIs, conformances, generics, and inheritance relationships.
  • Use the same local databases from the terminal CLI or from stdio MCP clients.

Installation

Install with Homebrew and download the pre-built databases:

brew tap mihaelamj/tap
brew install cupertino
cupertino setup

Add Cupertino to Claude Code:

claude mcp add cupertino --scope user -- $(which cupertino)

For JSON-based MCP clients, use the installed binary path:

{
  "mcpServers": {
    "cupertino": {
      "command": "/opt/homebrew/bin/cupertino",
      "args": ["serve"]
    }
  }
}

Codex users should include --no-reap as documented upstream:

codex mcp add cupertino -- $(which cupertino) serve --no-reap

Restart the MCP client after adding the server.

Use Cases

  • Ask Claude to look up current SwiftUI, UIKit, AppKit, Foundation, or platform-framework APIs.
  • Check Human Interface Guidelines while designing an Apple-platform interface.
  • Find Swift Evolution proposals related to a language feature.
  • Search Apple sample code before implementing a framework integration.
  • Compare framework availability across iOS, macOS, tvOS, watchOS, visionOS, or Swift versions.
  • Keep local documentation access available during offline development.
  • Give an agent deterministic Apple API context before it proposes code.

Safety and Privacy

Cupertino primarily serves public documentation from a local database, but documentation prompts can still disclose private development context. Keep proprietary source code, unreleased app plans, customer requirements, private bundle identifiers, and internal roadmap details out of prompts unless that disclosure is approved.

The initial setup downloads a large bundle and self-refresh workflows can crawl public documentation sources. Review disk space, cache locations, organization network policy, and Apple documentation terms before using it on shared or managed machines.

Documentation can change quickly around new platform releases. Verify compatibility-sensitive, beta, deprecated, or security-relevant guidance against live Apple documentation before shipping code.

Duplicate Check

content/mcp/apple-docs-mcp-server.mdx already covers kimsungwhee/apple-docs-mcp, an npm-based third-party Apple Docs server. Cupertino is a distinct implementation from mihaelamj/cupertino: it is a Swift CLI plus MCP server with a local offline documentation bundle, per-source SQLite indexes, HIG, Swift Evolution, Swift.org, Swift Book, Swift package, sample-code, and AST-symbol search coverage. No mihaelamj/cupertino entry or matching source URL was found in content/mcp.

Source citations

Add this badge to your README

Show that Cupertino MCP Server is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/mcp/cupertino-mcp-server.svg)](https://heyclau.de/entry/mcp/cupertino-mcp-server)

How it compares

Cupertino MCP Server side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.

1 trust signal differ across this comparison (Submitter).

Field

Local Apple documentation CLI and MCP server that gives Claude searchable offline access to Apple Developer Documentation, Swift Evolution proposals, Human Interface Guidelines, sample code, Swift.org pages, the Swift Book, and Swift package metadata.

Open dossier

Third-party MCP server for searching Apple Developer Documentation, framework APIs, Swift and Objective-C references, sample code, platform compatibility, documentation updates, and WWDC session data.

Open dossier

Official AWS Labs fully-managed remote MCP server providing up-to-date AWS documentation, code samples, agent skills, API and CloudFormation regional availability, and CDK/Amplify/Strands guidance over a hosted HTTP endpoint.

Open dossier

Context7 MCP server by Upstash that pulls up-to-date, version-specific library documentation and code examples directly into Claude's context so answers match the libraries you actually use.

Open dossier
Next steps
Trust
Review statusNot reviewedNot reviewedNot reviewedNot reviewed
Package trustPackage not verifiedPackage not verifiedPackage not verifiedPackage not verified
Source provenanceSource-backedSource-backedSource-backedSource-backed
SubmitterDiffersoktofeesh1oktofeesh1jaso0n0818glorydavid03023
Install riskReview firstReview firstReview firstReview first
Notes Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓
BrandAWS Labs logoAWS Labs
Categorymcpmcpmcpmcp
SourceSource-backedSource-backedSource-backedSource-backed
AuthormihaelamjkimsungwheeAWS LabsUpstash
Added2026-06-062026-06-052026-06-212026-06-02
Platforms
Harness
Source repo
Safety notesCupertino is an independent third-party project, not an official Apple project. The setup flow downloads a large local documentation bundle; review available disk space and cache locations before installing on managed machines. Self-building or refreshing the corpus can crawl Apple documentation and related public sources; respect Apple site terms and internal network policies. Codex users should pass `serve --no-reap` because upstream documents Codex process spawning behavior that can otherwise close the transport during tool calls. Documentation answers can be stale or incomplete after Apple platform releases, so verify compatibility-sensitive API, beta, and deprecation guidance against live Apple documentation before shipping code.This is a third-party MCP server, not an official Apple project. The server retrieves public documentation and metadata, but user queries can still reveal private project context to the MCP client, model provider, logs, and network services. Documentation answers should be checked against the live Apple documentation before shipping platform-specific, beta, deprecated, or compatibility-sensitive code. Use `@latest` intentionally when you want the newest package; pin a version when reproducible builds or locked team tooling are required.This is a fully managed remote server hosted by AWS; it serves public AWS knowledge and requires no AWS account or credentials, so do not add AWS access keys for it. Because it is a remote server, your queries are sent to the AWS-hosted endpoint; only connect clients you trust to route requests there. Generative output about AWS APIs and resources can still be wrong; verify guidance against the official AWS documentation it links.Makes outbound network requests to the Context7 service to resolve libraries and fetch documentation. Returned documentation and code snippets are third-party content; review examples before running them in your project.
Privacy notesCupertino serves local public documentation over stdio, but prompts and tool results can still expose app architecture, API choices, platform targets, package interests, and sample-code queries to the MCP client, model provider, and logs. The server writes operational output to stderr and uses structured logging; avoid including proprietary source code, unreleased product names, customer data, private bundle identifiers, or internal roadmap details in documentation prompts. Local databases and bundle paths may reveal the developer's Apple-platform focus or package interests to anyone with access to the machine or MCP client logs.Prompts and tool calls may include framework names, API choices, platform targets, WWDC interests, sample-code requests, app architecture details, feature plans, and compatibility constraints. MCP client logs and model transcripts can retain documentation queries and returned API text outside Apple's documentation site. Avoid sending proprietary source code, unreleased product names, customer requirements, private bundle identifiers, or internal roadmap details when a public documentation lookup is enough.Your documentation queries and search terms are sent over HTTPS to the AWS-hosted knowledge endpoint to retrieve content. The server returns public AWS documentation, code samples, and availability data; it does not read any private account data.The library names and documentation topics you query are sent to the Context7 service to return matching docs. Avoid placing secrets or private identifiers in the library queries passed to the server.
Prerequisites
  • macOS with Cupertino's current upstream-supported binary or build toolchain.
  • Homebrew or a manual install path for the Cupertino binary.
  • Approximately 4.2 GB of free disk space for the full pre-built documentation bundle.
  • Network access for the initial database download, or time to crawl and index the documentation sources yourself.
  • Node.js and npx available for running the npm package.
  • An MCP client that supports stdio servers, such as Claude Code, Claude Desktop, Cursor, VS Code, Windsurf, Zed, or Cline.
  • Network access to retrieve public Apple Developer Documentation, sample-code, and WWDC metadata.
  • Agreement on whether user prompts may include private project names, unreleased app details, or proprietary API usage questions.
  • An MCP client that supports remote HTTP MCP servers (or `uvx`/`fastmcp` to proxy the endpoint to stdio for clients that don't).
  • Outbound HTTPS access to the hosted endpoint `https://knowledge-mcp.global.api.aws`.
  • Node.js 18+ and npx available (verify with: npx --version)
  • Claude Code or Claude Desktop with MCP support
  • Internet access so the server can reach the Context7 documentation service
  • Optional Context7 API key for higher rate limits; the server also works without one
Install
brew tap mihaelamj/tap && brew install cupertino && cupertino setup
claude mcp add apple-docs -- npx -y @kimsungwhee/apple-docs-mcp@latest
uvx fastmcp run https://knowledge-mcp.global.api.aws
claude mcp add context7 -- npx -y @upstash/context7-mcp
Config
{
  "mcpServers": {
    "cupertino": {
      "command": "/opt/homebrew/bin/cupertino",
      "args": [
        "serve"
      ],
      "type": "stdio"
    }
  }
}
{
  "mcpServers": {
    "apple-docs": {
      "command": "npx",
      "args": [
        "-y",
        "@kimsungwhee/apple-docs-mcp@latest"
      ],
      "type": "stdio"
    }
  }
}
{
  "mcpServers": {
    "aws-knowledge-mcp-server": {
      "url": "https://knowledge-mcp.global.api.aws",
      "type": "http"
    }
  }
}
{
  "mcpServers": {
    "context7": {
      "command": "npx",
      "args": [
        "-y",
        "@upstash/context7-mcp"
      ],
      "type": "stdio"
    }
  }
}
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed
Open 4 picks in the interactive comparison tool

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.