ShipSwift vs WeJob
A side-by-side look at the ShipSwift and WeJob MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose ShipSwift for developer tools work over a hosted endpoint; choose WeJob 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 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.
Choose WeJob when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a remote HTTP/SSE transport.
- Its auth model fits you: No auth required.
- You want tools like
search, fetch, wejob_search_jobs.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Developer Tools | Developer Tools |
| Quality signal | 65/100 · Great | 69/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Remote HTTP/SSE |
| Auth | Not declared | No auth required |
| Pricing | Not declared | Free |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 3,245 | 1 |
| Directory activity | 4 views 0 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | 3 | 8 |
| Full listing | View ShipSwift | View WeJob |
Tools & capabilities
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.
WeJob tools 8
searchSearch public WeJob jobs, formations, and companies. Returns ids usable with fetch.fetchFetch a public WeJob item by id. Supported id prefixes: job:, formation:, company:.wejob_search_jobsSearch public active WeJob job offers.wejob_get_jobFetch one public active WeJob job offer by public id (raw id or the job:<id> returned by search/fetch).wejob_search_formationsSearch public active WeJob formations.wejob_get_formationFetch one public active WeJob formation by public id (raw id or the formation:<id> returned by search/fetch).wejob_search_companiesSearch public WeJob company profiles.wejob_get_companyFetch one public WeJob company profile by public id (raw id or the company:<id> returned by search/fetch).
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.
ShipSwift
{
"mcpServers": {
"shipswift": {
"url": "https://api.shipswift.app/mcp"
}
}
}
WeJob
{
"mcpServers": {
"wejob": {
"url": "https://mcp.wejob.ch/mcp"
}
}
}
Frequently asked questions
ShipSwift is categorized under Developer Tools and uses a remote HTTP/SSE transport. WeJob belongs to Developer Tools and uses a remote HTTP/SSE transport. Pick ShipSwift for developer tools work and WeJob 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.
ShipSwift has no declared pricing — check the project's own site. WeJob is listed as free. Auth: no auth required. 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 shipswift and wejob as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, ShipSwift has a quality signal of 65/100 (Great) with 4 views, 0 installs and 3,245 GitHub stars. WeJob has 69/100 (Great) with 1 views, 0 installs and 1 GitHub stars.