ShipSwift

ShipSwift acts as an MCP server that leverages the ShipSwift Skills integration to expose the AI-enabled SwiftUI component library as recipes and capabilities that your AI can request and fetch. The server enables discovery of available recipes, retrieval of specific recipe implementations, and searching across recipes provided by the ShipSwift Skills package. Use the MCP tooling to query for recipes like listRecipes, getRecipe, and searchRecipes, then instruct your AI to request the appropriate recipe and incorporate the SwiftUI components into your app-building prompts. The Skills integration handles provisioning and linking the ShipSwift components with your AI workflows, so you can ask for ready-to-use SwiftUI components, animations, charts, or multi-file modules via natural language prompts and receive code snippets, usage guidance, and implementation steps.

Prerequisites:

• Node.js (recommended LTS) and npm/yarn installed on your machine.
• Access to run npx commands in your environment.

Installation steps:

1. Install the ShipSwift MCP server via the Skills integration:

npx skills add signerlabs/shipswift-skills

2. Verify installation by listing available MCP endpoints (if your setup provides a quick-start check):

npx skills list --package signerlabs/shipswift-skills

3. Start using the ShipSwift MCP server in your AI pipelines by delegating recipe queries to the installed Skills integration and (optionally) configuring any required authentication or transport settings as documented by the Skills package.

Note: The exact start/run commands may vary depending on how your environment exposes the MCP endpoints from the ShipSwift Skills package. Refer to the Skills repository linked in the ShipSwift README for any environment-specific instructions.

Tips and potential issues:

• Ensure your Node.js and npm versions meet the minimum requirements for the skills package used by ShipSwift.
• If you encounter network or permission errors with npx, try clearing npm cache or using a node version manager (e.g., nvm).
• The ShipSwift MCP integration relies on the ShipSwift Skills package; keep it up to date to access new recipes, components, and backend wiring improvements.
• If your environment blocks internet access, download the skills package locally and point npx to a local cache or use an offline workflow as per your organization's policies.
• Environment variables you might configure (if needed) include API endpoints for the MCP server, authentication tokens for the Skills backend, and any proxy settings required by your network.
• When integrating with AI prompts, prefer explicit prompts like: "listRecipes", "getRecipe for LineChart", or "searchRecipes with keyword: 'Chart'" to leverage the MCP capabilities effectively.