Blog vs ShipSwift
A side-by-side look at the Blog 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 Blog 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 Blog when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
list_posts, search_posts, get_post.
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 | 55/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 | 0 | 3,245 |
| Directory activity | 1 views 0 installs 0 upvotes | 4 views 0 installs 0 upvotes |
| Tools | 8 | 3 |
| Full listing | View Blog | View ShipSwift |
Tools & capabilities
Blog tools 8
list_postsList the most recent posts on the Radixia blog (AI, serverless, open source, cloud). Returns title, slug, date, tags and excerpt for each.search_postsFull-text search across all Radixia blog posts (title, excerpt and body). Use this to find what Radixia has written about a topic, e.g. 'MCP', 'Bedrock', 'event driven'.get_postRead the full text of a Radixia blog post by its slug (get the slug from list_posts or search_posts).list_tagsList the topic tags used on the Radixia blog, with post counts.search_conference_transcriptsFull-text search across 147 auto-generated session transcripts from the technical conferences Radixia attends: keynotes, panels, vendor talks, research papers. Returns matching passages with session title, day/time/hall and recording timestamp. Quoted phrases must match exactly.get_conference_sessionRead the full auto-generated transcript of one conference session by (part of) its title. Use search_conference_transcripts or get_conference_agenda first to find session titles.get_conference_agendaThe program of the conference sessions currently indexed: session blocks with times, halls, types and speakers, plus the recorded research-paper talks. Optionally filter by day.about_radixiaWho is Radixia? Company profile: the four capabilities, leadership, Labs, ecosystem and contacts.
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.
Blog
{
"mcpServers": {
"blog": {
"url": "https://mcp.radixia.ai/mcp"
}
}
}
ShipSwift
{
"mcpServers": {
"shipswift": {
"url": "https://api.shipswift.app/mcp"
}
}
}
Frequently asked questions
Blog 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 Blog 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.
Blog 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 blog and shipswift as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Blog has a quality signal of 55/100 (Good) with 1 views, 0 installs and 0 GitHub stars. ShipSwift has 65/100 (Great) with 4 views, 0 installs and 3,245 GitHub stars.