MCP Geo1 Server

Exposes geolocation data to AI models via an MCP interface using EdgeOne Pages Functions.
  • typescript

0

GitHub Stars

typescript

Language

5 months ago

First Indexed

2 months ago

Catalog Refreshed

Documentation & install

Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.

Installation

Add the following to your MCP client configuration file.

Configuration

View docs
{
  "mcpServers": {
    "oldandoutdated-mcp-geo1": {
      "command": "tsx",
      "args": [
        "path/to/mcp-server/index.ts"
      ]
    }
  }
}

This MCP server exposes a geolocation tool that retrieves user location data via EdgeOne Pages Functions and makes it available to large language models through the Model Context Protocol (MCP). It enables AI workflows to tailor responses based on the requester’s location, powering smarter, location-aware interactions.

How to use

You will use the Geolocation MCP servant to access up-to-date location data from the EdgeOne Pages Function. The server implements a get_geolocation tool that AI models can call to retrieve information such as country, region, city, and coordinates when available. To use it, load the MCP server into your environment and reference the get_geolocation tool from your MCP client or integration. The tool is designed to be invoked by your model’s context when it needs location data to inform responses or decisions.

How to install

Prerequisites: ensure you have a runtime environment capable of running TypeScript-based MCP components, and a mechanism to host or request MCP endpoints. You will use the provided MCP configuration to register the geolocation MCP server.

  1. Create or open your MCP configuration file. 2) Add the following MCP server entry to declare the local (stdio) server that runs the TypeScript entry point.
{
  "mcpServers": {
    "edgeone_geo_mcp": {
      "command": "tsx",
      "args": ["path/to/mcp-server/index.ts"]
    }
  }
}

Notes on running

The server is started by executing the runtime command shown in the configuration. Ensure the path to the MCP entry file is correct for your project structure. If you use a separate process runner or orchestration tool, keep the same command and arguments so the MCP client can initialize and communicate with the get_geolocation tool.

Additional notes

Security: limit access to the geolocation data to trusted MCP clients and models. Validate that requests are authenticated and that location data is used in compliance with privacy policies. Logging should be configured to avoid exposing sensitive user information.

Available tools

get_geolocation

A tool exposed by the MCP server that retrieves user geolocation information through the integrated EdgeOne Pages Function.

Built by
VeilStrat
AI signals for GTM teams
© 2026 VeilStrat. All rights reserved.All systems operational