Aicanvas vs ShipSwift
A side-by-side look at the Aicanvas and ShipSwift MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Aicanvas for developer tools work as a local process; choose ShipSwift for developer tools over a hosted endpoint. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Aicanvas when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
Choose ShipSwift when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
listRecipes, getRecipe, searchRecipes.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 49/100 · Fair | 65/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Remote HTTP/SSE |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 68 | 3,245 |
| Directory activity | 1 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | Not listed | 3 |
| Full listing | View Aicanvas | View ShipSwift |
Tools & capabilities
Aicanvas tools
No tool names declared yet. Check the project README from the listing page.
ShipSwift tools 3
listRecipesList production-ready SwiftUI code recipes. Each recipe is a complete, copy-paste-ready implementation — not a tutorial. Covers native iOS features (SwiftUI, Swift Charts, SpriteKit, Vision, AVFoundation, StoreKit 2, NavigationStack) and backend infrastructure (AWS CDK, Hono, Node.js, Cognito, DynamoDB). Categories: animations, charts, UI components, and full-stack modules including auth, camera, subscriptions, chat, and settings.getRecipeGet a recipe by ID. Returns complete, copy-paste-ready Swift source code with architecture explanation and implementation steps. Module recipes may also include backend code (Hono/Node.js + AWS CDK).searchRecipesSearch recipes by keyword across titles, descriptions, tags, and full source code. Use for any iOS, SwiftUI, or backend topic — e.g. subscription, authentication, camera, animation, chart, onboarding, paywall, infrastructure.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Aicanvas
{
"mcpServers": {
"aicanvas": {
"command": "npx",
"args": [
"-y",
"shadcn@latest"
]
}
}
}
ShipSwift
{
"mcpServers": {
"shipswift": {
"url": "https://api.shipswift.app/mcp"
}
}
}
Frequently asked questions
Aicanvas is categorized under Developer Tools and uses a local stdio subprocess. ShipSwift belongs to Developer Tools and uses a remote HTTP/SSE transport. Pick Aicanvas for developer tools work and ShipSwift for developer tools.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Aicanvas has no declared pricing — check the project's own site. ShipSwift has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add aicanvas and shipswift as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Aicanvas has a quality signal of 49/100 (Fair) with 1 views, 0 installs and 68 GitHub stars. ShipSwift has 65/100 (Great) with 4 views, 0 installs and 3,245 GitHub stars.