MCP server

ShipSwift MCP Server: SwiftUI Components and Recipes

ShipSwift gives an AI coding agent a SwiftUI component library and full-stack recipes through a hosted MCP server, so iOS UI is fetched from real source instead of guessed.

Run
claude mcp add --transport http shipswift https://api.shipswift.app/mcp
View on GitHub

Stars, license and last push from GitHub. Install count as reported by the open skills directory.

What is the ShipSwift MCP server?

ShipSwift is an AI-native SwiftUI component library with a hosted MCP server. An AI coding agent can list, search and fetch recipes, each with SwiftUI source, implementation steps and best practices, covering animations, charts, UI components and modules like auth, camera and chat. The iOS client code is MIT-licensed.

ShipSwift describes itself as an AI-native SwiftUI component library with full-stack recipes. The recipe server is a hosted MCP endpoint at api.shipswift.app. Your AI coding agent connects to it and retrieves complete SwiftUI source for a component, plus implementation steps and best practices.

The library is organized as SWAnimation, SWChart, SWComponent, SWModule and SWUtil. The README counts 30 animation components, including Metal-shader backgrounds, plus charts, display, feedback and input components, and modules such as authentication, camera, chat and settings.

What changes in your agent's output

  • A request like adding a shimmer loading animation returns a recipe with real SwiftUI code instead of a generic guess.
  • Everything shares the SW naming convention and dependency rules, so generated code stays consistent across screens.
  • Charts, onboarding, steppers and FAQ views come as self-contained files you can copy into an Xcode project.
  • Pro recipes add backend guides, compliance templates and known pitfalls for subscriptions, TikTok tracking and export.

Free and Pro recipes

All iOS client code is open source under the MIT license. The README separates free recipes from Pro ones. Pro adds backend implementation such as Hono routes and database schema, integration guides, compliance templates and pitfall guides. Without the MCP server, local skills read the source files straight from the repository.

Who ShipSwift MCP is for

Best for

  • iOS developers building SwiftUI apps who want ready animations, charts and onboarding screens.
  • Teams that prototype in the Simulator and want an agent to assemble screens from known components.
  • Developers who want one place for UI and the wiring behind it, such as auth, paywalls and chat.

Not for

  • Web, React or Tailwind projects. For those, see the shadcn MCP server or Magic MCP.
  • Reading a design file. The Figma MCP server is the right source when the design lives in Figma.
  • Android and cross-platform apps. The library is SwiftUI, targeting iOS 18 and later per the README badge.

Use it with UiChemy

ShipSwift builds native iOS screens. If your project is a WordPress site, UiChemy covers that side: Composer edits inside Elementor or Gutenberg, and Figma to WordPress turns a design into editable pages. Click Get Started on uichemy.com.