Xmp4 — Semantic Code Intelligence vs ShipSwift
A side-by-side look at the Xmp4 — Semantic Code Intelligence 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 Xmp4 — Semantic Code Intelligence for developer tools work over a hosted endpoint; 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 Xmp4 — Semantic Code Intelligence when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
xmp4_callees, xmp4_callers, xmp4_deps.
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 | 53/100 · Good | 65/100 · Great |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | 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 | 1 | 3,244 |
| Directory activity | 1 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | 16 | 3 |
| Full listing | View Xmp4 — Semantic Code Intelligence | View ShipSwift |
Tools & capabilities
Xmp4 — Semantic Code Intelligence tools 16
xmp4_calleesFind direct callees (methods called by) a symbol in a project. Navigate step-by-step by calling xmp4_callees again on interesting results.xmp4_callersFind direct callers of a symbol in a project. Navigate step-by-step by calling xmp4_callers again on interesting results.xmp4_depsList external dependencies of a project.xmp4_grepServer-side regex text search over indexed project source files. Free tier: requires file_path (single file). Premium tier (XMP4_PREMIUM_GREP_WALK=true): allows file_glob multi-file walk. Prefer xmp4_tests_for/xmp4_usages for SCIP symbols — grep is for text not indexed (comments, literals, config keys).xmp4_guideUsage guide for xmp4 tools — read this first to learn the correct workflowxmp4_hierarchyGet type hierarchy (base, interfaces, derived) for a symbol in a project.xmp4_infoGet detailed information about a symbol in a project.xmp4_outlineGet outline (all symbols) for a file in a project.xmp4_projectsSearch and browse projects by language and name. Use this first to discover projects, then use other tools with the repo name.xmp4_searchSearch symbols in a project. Use xmp4_projects first to find the project identifier.xmp4_serverGet server information, version, and capabilitiesxmp4_sourceExtract source code for a symbol in a project.- +4 more on 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.
Xmp4 — Semantic Code Intelligence
{
"mcpServers": {
"xmp4-semantic-code-intelligence": {
"url": "https://mcp.example4.ai/mcp"
}
}
}
ShipSwift
{
"mcpServers": {
"shipswift": {
"url": "https://api.shipswift.app/mcp"
}
}
}
Frequently asked questions
Xmp4 — Semantic Code Intelligence is categorized under Developer Tools and uses a remote HTTP/SSE transport. ShipSwift belongs to Developer Tools and uses a remote HTTP/SSE transport. Pick Xmp4 — Semantic Code Intelligence 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.
Xmp4 — Semantic Code Intelligence 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 xmp4-semantic-code-intelligence and shipswift as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Xmp4 — Semantic Code Intelligence has a quality signal of 53/100 (Good) with 1 views, 0 installs and 1 GitHub stars. ShipSwift has 65/100 (Great) with 4 views, 0 installs and 3,244 GitHub stars.