# SwiftPieces MCP server

> Search and install free SwiftUI components for iOS apps, with source, docs and Liquid Glass guidance.

- Listing: https://mcp.tc/i/swiftpieces
- Connect: use the server's own URL `https://swiftpieces.com/api/mcp` (no sign-in); clients connect to it directly. The listing link is a page, not an MCP endpoint.
- Type: remote (Streamable HTTP)
- Auth: none
- Category: [Developer Tools](https://mcp.tc/c/developer-tools)
- Vendor: SwiftPieces
- Homepage: <https://swiftpieces.com/>

## About

Connects an AI assistant to the free SwiftPieces registry of single-file SwiftUI components for iOS. You can search pieces and blocks by keyword or category, read a piece's full source and metadata, and get the files to write into an Xcode 16 synchronized folder. It also returns a guide to correct Liquid Glass adoption on iOS 26.

Runs as a hosted streamable HTTP endpoint at https://swiftpieces.com/api/mcp. No sign-in or API key is needed. SwiftPieces Pro screens, patterns, flows and templates use a separate Pro server that needs a license key.

## What it can do

- Search free SwiftUI pieces by keyword, category or minimum iOS version
- Search blocks (whole screen sections) by keyword or category
- Fetch a piece's full source, shaders, metadata and docs URL
- Get files to write for installing a piece into an Xcode project
- List piece and pattern categories with counts
- Read verified iOS 26 Liquid Glass adoption rules

## Tools (7)

- `get_design_skill`: App Design: the free SwiftPieces design method for any SwiftUI app.
- `search_pieces`: Search the free SwiftPieces registry by keyword, with optional category and minimum iOS filters.
- `search_blocks`: Search patterns (whole screen sections) by keyword or category; most are in Pro.
- `get_piece`: Return a free piece's or block's full source, shaders, metadata and docs URL.
- `install_piece`: Return files to write for installing a piece or block into an Xcode 16 folder, plus the CLI command.
- `list_categories`: List free piece and pattern categories with counts and links to the Pro library.
- `get_liquid_glass_guide`: Return rules for correct Liquid Glass adoption with verified iOS 26 API names.

## Example prompts

- "Find a SwiftUI piece for a swipeable card deck that works on iOS 17"
- "Install the Parallax Card piece into my Xcode project"
- "Add a chart I can scrub with my thumb"
- "Show me the rules for adopting Liquid Glass correctly on iOS 26"

## Install

### Claude Code

1. Run this in a terminal, in your project folder:

```bash
claude mcp add --transport http swiftpieces https://swiftpieces.com/api/mcp
```

2. Start Claude Code and type `/mcp`. **swiftpieces** should show as connected.

Add `--scope user` to make it available in every project, not just this one.

### Claude Desktop

1. Open **Customize → Connectors**, click **+ Add**, then **Add custom connector**.

2. Name it **SwiftPieces** and paste this URL:

```url
https://swiftpieces.com/api/mcp
```

3. Click **Add**. Its tools appear in the chat’s tools menu.

Claude Desktop’s JSON config file only starts local servers. Remote servers go through Connectors, and connectors you add on claude.ai show up here too.

### claude.ai

1. Open the connector form on claude.ai. This button fills in the name and URL for you:

[Add to claude.ai](<https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=SwiftPieces&connectorUrl=https%3A%2F%2Fswiftpieces.com%2Fapi%2Fmcp>) (opens connector settings)

2. Check that the URL reads `https://swiftpieces.com/api/mcp` and click **Add**.

3. Turn it on in a chat from the tools menu.

Free plans allow one custom connector. On Team and Enterprise plans an owner adds it under **Organization settings → Connectors**.

### ChatGPT

1. On chatgpt.com, go to **Plugins**, select **+**, then **Add custom MCP server**.

2. Enter a name for the server.

3. Under **Connection**, paste `https://swiftpieces.com/api/mcp` as the server URL, then for authentication choose **No authentication**.

4. Check **I understand and want to continue**, then select **Create as a plugin**.

Whether you can add a custom MCP server depends on your ChatGPT plan and your workspace permissions (in Business workspaces, admins and owners can).

### Cursor

[Add to Cursor](<https://cursor.com/install-mcp?name=swiftpieces&config=eyJ1cmwiOiJodHRwczovL3N3aWZ0cGllY2VzLmNvbS9hcGkvbWNwIn0%3D>) (opens Cursor)

Or add it by hand to `~/.cursor/mcp.json` (all projects) or `.cursor/mcp.json` (this project):

`mcp.json`:

```json
{
  "mcpServers": {
    "swiftpieces": {
      "url": "https://swiftpieces.com/api/mcp"
    }
  }
}
```

### VS Code

[Install in VS Code](<https://vscode.dev/redirect/mcp/install?name=swiftpieces&config=%7B%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fswiftpieces.com%2Fapi%2Fmcp%22%7D>) (opens VS Code)

Or from a terminal:

```bash
code --add-mcp '{"name":"swiftpieces","type":"http","url":"https://swiftpieces.com/api/mcp"}'
```

Or commit it to the repo in `.vscode/mcp.json`:

`.vscode/mcp.json`:

```json
{
  "servers": {
    "swiftpieces": {
      "type": "http",
      "url": "https://swiftpieces.com/api/mcp"
    }
  }
}
```

### Devin Desktop

1. Add it to `~/.config/devin/mcp_config.json` (macOS and Linux) or `%APPDATA%\devin\mcp_config.json` (Windows):

`mcp_config.json`:

```json
{
  "mcpServers": {
    "swiftpieces": {
      "serverUrl": "https://swiftpieces.com/api/mcp"
    }
  }
}
```

2. Refresh the MCP server list in Cascade.

Devin Desktop is the new name for Windsurf. It reads `serverUrl` (or `url`) for remote servers.

### Codex

```bash
codex mcp add swiftpieces --url https://swiftpieces.com/api/mcp
```

Or edit `~/.codex/config.toml` directly:

`config.toml`:

```toml
[mcp_servers.swiftpieces]
url = "https://swiftpieces.com/api/mcp"
```

### Gemini CLI

```bash
gemini mcp add --transport http swiftpieces https://swiftpieces.com/api/mcp
```

This adds it to the current project. Add `-s user` to use it everywhere.

### Any client

Most clients accept this shape. Some name the URL field differently: `serverUrl` in Devin Desktop, `httpUrl` in Gemini CLI’s settings file.

```json
{
  "mcpServers": {
    "swiftpieces": {
      "type": "http",
      "url": "https://swiftpieces.com/api/mcp"
    }
  }
}
```

Zed puts servers under `context_servers` in its settings. Cline needs `"type": "streamableHttp"`, or it assumes SSE.

Client only starts local servers? Bridge it with `npx -y mcp-remote https://swiftpieces.com/api/mcp`.

## Recent changes

- 2026-11-12 20:50 UTC: New version 0.2.0 (was 0.1.0), reported by the server. Source: automatic check.
- 2026-11-12 20:50 UTC: 1 tool added. Server instructions changed. Source: automatic check. Worth a look: new server instructions. Added: get\_design\_skill.
- 2026-10-28 14:24 UTC: Tracking started: 6 tools read. Source: automatic check.

More on the History tab, with descriptions before and after for the newest entries: https://mcp.tc/i/swiftpieces#history (Atom feed: https://mcp.tc/i/swiftpieces/history.xml). It records what mcp.tc's anonymous checks saw, every 3 hours where the tool list can be read without sign-in; it is not a security review.

## Details

- Server version: 0.2.0
- MCP protocol version: 2025-06-18
- Last checked: 2026-11-18 (reachable)
- Listed: 2026-10-28
- Updated: 2026-11-12

---
Source: https://mcp.tc/i/swiftpieces (mcp.tc is an independent directory, not affiliated with this server's publisher). Corrections: https://mcp.tc/report
