Magic MCP vs Geoapify
A side-by-side look at the Magic MCP and Geoapify MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Magic MCP for architecture & design work as a local process; choose Geoapify for location services as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Magic MCP when
- You need dedicated capabilities in the Architecture & Design domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
TWENTY_FIRST_API_KEY, API_KEY_21ST.
Choose Geoapify when
- You need dedicated capabilities in the Location Services domain.
- You prefer a local stdio subprocess transport.
- You want tools like
geocode, reverse_geocode, places.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Architecture & Design | Location Services |
| Quality signal | 53/100 · Good | 59/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | Not declared |
| Pricing | Paid service | Not declared |
| Required env vars | TWENTY_FIRST_API_KEYAPI_KEY_21ST | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 6,217 | 0 |
| Directory activity | 16 views 1 installs 0 upvotes | 1 views 0 installs 0 upvotes |
| Tools | Not listed | 4 |
| Full listing | View Magic MCP | View Geoapify |
Tools & capabilities
Magic MCP tools
No tool names declared yet. Check the project README from the listing page.
Geoapify tools 4
geocodeForward geocoding: convert an address, place name, or freeform location text into geographic coordinates (latitude/longitude). Returns matched candidates with formatted address, lat, lon, country, city, and postcode. Example: geocode({ text: "1600 Amphitheatre Parkway, Mountain View, CA" })reverse_geocodeReverse geocoding: convert latitude/longitude coordinates into the nearest street address. Returns formatted address, country, city, street, house number, and postcode. Example: reverse_geocode({ lat: 48.8584, lon: 2.2945 })placesSearch for places and points of interest (POI) near a location, filtered by Geoapify category. Returns name, formatted address, categories, lat, lon, and distance from the center point. Example: places({ categories: "catering.restaurant", lat: 48.8584, lon: 2.2945, radius: 1000 })routingRouting / directions: compute the distance and travel time between two points for a given travel mode (drive, walk, bicycle, transit). Returns distance in meters and time in seconds. Example: routing({ from_lat: 48.8584, from_lon: 2.2945, to_lat: 48.8606, to_lon: 2.3376, mode: "drive" })
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.
Magic MCP
{
"mcpServers": {
"21st-dev-magic-mcp": {
"command": "npx",
"args": [
"-y",
"@21st-dev/cli@latest"
],
"env": {
"TWENTY_FIRST_API_KEY": "YOUR_TWENTY_FIRST_API_KEY_HERE",
"API_KEY_21ST": "YOUR_API_KEY_21ST_HERE"
}
}
}
}
Geoapify
{
"mcpServers": {
"geoapify": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-geoapify"
]
}
}
}
Frequently asked questions
Magic MCP is categorized under Architecture & Design and uses a local stdio subprocess. Geoapify belongs to Location Services and uses a local stdio subprocess. Pick Magic MCP for architecture & design work and Geoapify for location services.
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.
Magic MCP is listed as a paid service. Auth: api key required. Geoapify 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 21st-dev-magic-mcp and geoapify as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Magic MCP has a quality signal of 53/100 (Good) with 16 views, 1 installs and 6,217 GitHub stars. Geoapify has 59/100 (Good) with 1 views, 0 installs and 0 GitHub stars.