📝 mcp-ip-geo

Created By
chenmingyong0423a year ago
An MCP Server that provides IP geolocation lookup (country, region, city, etc.) via ip-api.com.
Overview

what is mcp-ip-geo?

mcp-ip-geo is an MCP Server that provides IP geolocation lookup (country, region, city, etc.) via ip-api.com.

how to use mcp-ip-geo?

To use mcp-ip-geo, you can build it from source using Go or Docker, or install it remotely using Go commands. The server can be configured to run locally or remotely.

key features of mcp-ip-geo?

  • Provides accurate IP geolocation data including country, region, and city.
  • Supports both local and remote server configurations.
  • Easy to deploy using Docker or Go commands.

use cases of mcp-ip-geo?

  1. Determining the geographical location of users based on their IP addresses.
  2. Enhancing user experience by personalizing content based on location.
  3. Analyzing traffic sources for web applications.

FAQ from mcp-ip-geo?

  • What kind of data can mcp-ip-geo provide?

mcp-ip-geo can provide geolocation data such as country, region, and city based on IP addresses.

  • Is mcp-ip-geo easy to deploy?

Yes! You can deploy it using Docker or Go commands, making it flexible for different environments.

  • Can I use mcp-ip-geo for commercial purposes?

No!This project uses the free version of ip-api.com, which is strictly limited to non-commercial use. If you intend to use this project for commercial purposes, please make sure to comply with their terms of service or purchase a commercial license: ip-api.com

Server Config

{
  "mcpServers": {
    "mcp-ip-geo": {
      "command": "/path/to/mcp-ip-geo"
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
chenmingyong0423
Star
8
Language
Go
License
MIT license
Category
Tags

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago