MCP Server Ipinfo vs Ipinfo
A side-by-side look at the MCP Server Ipinfo and Ipinfo MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose MCP Server Ipinfo for location services work; choose Ipinfo 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 MCP Server Ipinfo when
- You need dedicated capabilities in the Location Services domain.
- Its auth model fits you: API key required.
- You have the keys it needs:
IPINFO_API_TOKEN, IPINFO_CACHE_TTL, IPINFO_CACHE_SIZE. - You want tools like
IPDetails.ip, api_error, enterprise.
Choose Ipinfo when
- You need dedicated capabilities in the Location Services domain.
- You prefer a local stdio subprocess transport.
- You want tools like
lookup_ip, get_my_ip.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Location Services | Location Services |
| Quality signal | 49/100 · Fair | 52/100 · Good |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | API key required | Not declared |
| Pricing | BYOK (pay the provider) | Not declared |
| Required env vars | IPINFO_API_TOKENIPINFO_CACHE_TTLIPINFO_CACHE_SIZE | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 44 | 0 |
| Directory activity | 2 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 5 | 2 |
| Full listing | View MCP Server Ipinfo | View Ipinfo |
Tools & capabilities
MCP Server Ipinfo tools 5
IPDetails.ipapi_errorenterpriseMapResulttruncated
Ipinfo tools 2
lookup_ipGet geolocation and network info for any IP address (e.g., "8.8.8.8"). Returns city, region, country, coordinates, org, postal code, timezone.get_my_ipGet your current IP address with geolocation data. Returns city, region, country, coordinates, org, postal code, timezone.
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.
MCP Server Ipinfo
No confirmed install command for MCP Server Ipinfo yet — follow the setup steps linked from its listing page rather than a guessed package name.
Ipinfo
{
"mcpServers": {
"ipinfo": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-ipinfo"
]
}
}
}
Frequently asked questions
MCP Server Ipinfo is categorized under Location Services and uses an install path we have not confirmed yet. Ipinfo belongs to Location Services and uses a local stdio subprocess. Pick MCP Server Ipinfo for location services work and Ipinfo 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. MCP Server Ipinfo has no confirmed install command yet — follow its own setup instructions.
MCP Server Ipinfo is bring-your-own-key: usage is billed by the API provider you supply a key for. Auth: api key required. Ipinfo 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 briandconnelly-mcp-server-ipinfo and ipinfo as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, MCP Server Ipinfo has a quality signal of 49/100 (Fair) with 2 views, 0 installs and 44 GitHub stars. Ipinfo has 52/100 (Good) with 0 views, 0 installs and 0 GitHub stars.