Swiftforge

io.github.jrlingyin888Published by GitHub account jrlingyin888v0.2.1Updated Oct 24, 2026

Curated, current SwiftUI components (incl. iOS 26 Liquid Glass) for your AI coding agent.

VerifiedSTDIODesktop onlyKnowledge & MemoryDeveloper Tools

Overview

AI-generated overview

A local MCP server that gives a coding agent a curated catalog of modern SwiftUI components to browse, search and fetch as source code.

What you can do
Browse the catalog's categories and component counts, optionally filtered by category, to see what is available before choosing a component for a view or screen.
When to use it
Useful when an AI coding agent is building iOS or SwiftUI interfaces and you want it to pull current, reviewed components instead of guessing at APIs or reaching for deprecated ones.
Requirements
Runs as a local process over stdio, installed from the npm package swiftforge-mcp (for example via npx), so Node.js and npm are needed on the machine. No authentication, environment variables or headers are declared.
Before you install
The server only serves component source and notes; the agent still writes code into your project, so review what it inserts before building. The README's demo build was verified on Xcode 26 and an iOS 26 simulator, so older toolchains may not compile the newest components.

Installation

In SourceWeft

  1. Open Swiftforge in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

[SwiftForge logo]

SwiftForge MCP

[npm version] [license] [MCP] [SwiftUI]

A curated, current, production-grade SwiftUI component library — served straight to your AI coding agent over MCP.

Think 21st.dev (curated React components for AI agents), but for SwiftUI.


See it in action

https://github.com/user-attachments/assets/c2460a1d-fb0d-47e0-9d1b-91e6a784717b

A quick tour of components from the catalog (incl. iOS 26 Liquid Glass), running in the demo app.


The problem

Coding agents (Claude Code, Cursor, Copilot) are great at logic and mediocre at SwiftUI. They:

  • reach for deprecated APIs (NavigationView, .foregroundColor, ObservableObject everywhere)
  • have never seen iOS 26 "Liquid Glass" (.glassEffect, GlassEffectContainer, .buttonStyle(.glass)) and guess wrong
  • produce bland, one-off views instead of polished, reusable components

You end up rewriting their SwiftUI by hand. Every time.

What SwiftForge does

SwiftForge is a tiny MCP server that gives your agent on-demand access to a hand-curated catalog of modern, compile-ready SwiftUI components. When you ask your agent to "add a glass card" or "build an onboarding flow," it pulls the real, current component instead of hallucinating one.

The value isn't the server — it's the curated catalog: every component uses current API only, is dark-mode + Dynamic Type friendly, includes a #Preview, and is reviewed for taste.

Quick start

Claude Code

bash
claude mcp add swiftforge -- npx -y swiftforge-mcp

Cursor / Windsurf (~/.cursor/mcp.json or project .cursor/mcp.json)

json
{  "mcpServers": {    "swiftforge": {      "command": "npx",      "args": ["-y", "swiftforge-mcp"]    }  }}

Full setup, example prompts, and troubleshooting: docs/USAGE.md.

Run from a local clone (development)
bash
git clone <this repo> && cd swiftforge-mcpnpm install && npm run smoke# then point your agent at: node /absolute/path/to/src/index.js

Then just talk to your agent:

"Use swiftforge to add a Liquid Glass stat card to this dashboard." "Search swiftforge for a pull-to-refresh list and wire it to my view model."

Demo app — the closed loop, proven

examples/SwiftForgeDemo is a real iOS app that pulls in all 96 catalog components and builds clean — proof that the full loop works (agent → swiftforge → a compiling iOS app):

bash
npm run demo:gen      # (re)generate the demo project from the catalognpm run demo:build    # headless xcodebuild for the iOS simulator# or just open it:open examples/SwiftForgeDemo/SwiftForgeDemo.xcodeproj

Verified ** BUILD SUCCEEDED ** on Xcode 26 / iOS 26 simulator — including the Liquid Glass components. The app live-renders a couple of components (paywall, OTP) and lists the full catalog.

Tools the agent gets

ToolWhat it does
list_categoriesSee the catalog's categories + counts
list_componentsBrowse components (optionally by category)
search_componentsFree-text search by what you're building
get_componentFetch one component's full, current SwiftUI source + usage + notes

What's inside

96 curated components across 14 categories: Buttons & Controls · Cards & Containers · Navigation & Bars · Lists & Scroll · Lists & Grids · Forms & Inputs · Charts · Effects & Liquid Glass · Feedback & Overlays · Media · Auth & Account · Animations · Layout & Scaffolding · Onboarding & Hero — including dedicated iOS 26 Liquid Glass components with graceful-fallback notes.

Every component is gated through a syntax check (scripts/validate.js, xcrun swiftc -parse) and a senior-review pass that strips deprecated API.

📖 Browse every component → docs/CATALOG.md

Roadmap

  • New components every release, kept current as iOS evolves.
  • Missing something? Open an issue — requests drive what gets added next.

The catalog here is free and MIT.

License

MIT (server). Catalog content © its authors.

Source: README.md at commit eca0728

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.2.1LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts