Ip Api vs Opencages
A side-by-side look at the Ip Api and Opencages MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Ip Api for location services work over a hosted endpoint; choose Opencages 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 Ip Api when
- You need dedicated capabilities in the Location Services domain.
- You prefer a remote HTTP/SSE transport.
- You want tools like
lookup, batch.
Choose Opencages when
- You need dedicated capabilities in the Location Services domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
PLATFORM_OPENCAGE_KEY.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Location Services | Location Services |
| Quality signal | 41/100 · Fair | 41/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | PLATFORM_OPENCAGE_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 2 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 2 | Not listed |
| Full listing | View Ip Api | View Opencages |
Tools & capabilities
Ip Api tools 2
lookupGeolocation for an IP (or caller if ip omitted).batchBulk lookup (max 100 IPs).
Opencages tools
No tool names declared yet. Check the project README from the listing page.
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.
Ip Api
{
"mcpServers": {
"ip-api": {
"url": "https://gateway.pipeworx.io/ip-api/mcp"
}
}
}
Opencages
{
"mcpServers": {
"opencages": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-opencages"
],
"env": {
"PLATFORM_OPENCAGE_KEY": "YOUR_PLATFORM_OPENCAGE_KEY_HERE"
}
}
}
}
Frequently asked questions
Ip Api is categorized under Location Services and uses a remote HTTP/SSE transport. Opencages belongs to Location Services and uses a local stdio subprocess. Pick Ip Api for location services work and Opencages 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.
Ip Api has no declared pricing — check the project's own site. Opencages 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 ip-api and opencages as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Ip Api has a quality signal of 41/100 (Fair) with 2 views, 0 installs and 0 GitHub stars. Opencages has 41/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.