"Apple Pay" matching MCP servers:

Search and retrieve information from Apple's complete developer documentation, including API references, code examples, and Human Interface Guidelines, across all Apple platforms and versions.

Enables offline, real-time search of Apple Developer Documentation from Xcode's local index, returning full text, code examples, availability, and framework listings without network calls.

Apple developer documentation for coding agents: doc search with developer.apple.com's own results, a complete index of 336,629 pages read in full with signatures and OS availability, and Sample Code with 1,700 WWDC sessions (2014–2026) included. Helps agents write native Swift against current Apple APIs.

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.

Provides live Apple documentation fetching, Xcode build error analysis, and Swift Evolution proposal checking for Apple development assistance.

MCP server for Claude Desktop that exposes App Store Connect and RevenueCat APIs, enabling indie iOS developers to query portfolio metrics, sales reports, subscriptions, and customer reviews directly in chat.

Universal CLI and MCP server providing unified payment links, customer prefilling, expiring checkouts, refund management, fee comparison, and HMAC-verified webhook proxying across Stripe, Razorpay, and LemonSqueezy.

A high-performance MCP server for Apple Mail that uses optimized JavaScript for Automation (JXA) to search and manage emails. It enables users to list accounts, fetch mailboxes, and retrieve today's, unread, or flagged messages with significantly improved speed through batch property fetching.

A Model Context Protocol server that provides AI coding assistants with direct access to Apple's Developer Documentation, enabling seamless lookup of frameworks, symbols, and detailed API references.

Enables AI agents to search and retrieve Apple Developer Documentation instantly with symbol search, wildcard matching, and optional semantic embeddings.

Enables Claude Code users to search and read Apple Developer Documentation — frameworks, APIs, SwiftUI/UIKit symbols, Human Interface Guidelines, design resources, sample code, and WWDC session transcripts — directly in their session. It also retrieves code examples, platform compatibility, and related API information through Apple's documentation and search APIs.

Enables AI assistants to handle WeChat Pay V3 and Alipay signing, order creation, and callback verification locally without touching funds.

A local MCP server that lets AI coding assistants search Apple's Human Interface Guidelines catalog, fetch individual articles as Markdown, and read community implementation notes for native apps and the web. It enables guideline-grounded design, conversion, and auditing workflows across iOS, iPadOS, macOS, watchOS, tvOS, visionOS, and web platforms.

An MCP server that connects AI coding agents with Apple Notes for developer workflows like capturing debug sessions, logging commits, and saving code snippets.

Local MCP server for Apple platform console, unified, and diagnostic logs. Enables listing devices and capturing live logs from simulators and real devices.

Provides AI assistants with access to Apple's Human Interface Guidelines and technical API documentation across all Apple platforms (iOS, macOS, watchOS, tvOS, visionOS), enabling unified search of design principles and implementation details.

MCP server exposing the full Apple Ads (Search Ads) Campaign Management API v5 — 74 typed tools

A Model Context Protocol server for AI models to access and manipulate Apple Calendar data on macOS through a standardized interface.

Enables management of iOS/macOS apps, TestFlight builds, app metadata, analytics, and more through natural language interactions with Apple Store Connect API.

. A good description should be concise and describe what the server enables users to do, e.g. * Enables to interact with WordPress sites...' Then a huge block? Actually the user message includes the README content inside tags, then after the readme, there is a large block of text starting with '{