MCP and agents
Let Claude Code, Cursor or any MCP client find and install pieces for you.
The Pro MCP server gives coding agents the whole library. Use the same license key as the CLI; create one on your account page if you haven't (step 2 of the Quickstart).
Connect
claude mcp add --transport http swiftpieces-pro https://pro.swiftpieces.com/api/mcp --header "x-license-key: sp_live_..."Ask
Then ask in plain English, for example:
- "Add the Wallet screen from Swift Pieces Pro and show my accounts in it."
- "Set up onboarding with a paywall using Swift Pieces Pro."
- "Theme the installed pieces with our brand colors."
The agent searches the library, installs the piece and its dependencies, and reads the Build Kit so new code matches the pieces.
- "Use style-press and brief-shopping from the Swift Pieces Build Kit to build the store's home screen."
- "Follow recipe-send-money to add sending money to my Wallet tab."
Tools
| Tool | What it returns |
|---|---|
search_library | Pieces by keyword, type (screen, template) or category |
get_item | A piece's files and dependencies, by id such as wallet-stack |
list_kit | Build Kit styles, briefs, recipes and tools (public metadata) |
get_kit_item | One Build Kit item's full SKILL.md, by id such as style-press (swift-pieces is free) |
Prompts
Every Build Kit item is also an MCP prompt. Clients that support prompts show them as slash commands: in Claude Code, type /mcp__swiftpieces-pro__ and pick one, for example style-studio or tool-review. Add your task after the command and the agent follows the item for it.