Skip to main content
Glama
v5tech

Location MCP Server

by v5tech
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Remote

Location MCP Server

中文 / English

A location server based on MCP (Model Context Protocol) that provides IP address location and latitude/longitude query functionality.

Features

  • Support location query by IP address

  • Support detailed address query by latitude and longitude coordinates

  • Based on Meituan Open API

  • Developed with TypeScript for type safety

  • Compliant with MCP protocol standard

Installation

npm install @v8tech/mcp-server-location -g

Usage

The server provides two main tools:

  1. IP Location (ip_location)

    • Input: IP address

    • Output: Detailed location information including country, province, city, district, etc.

  2. Latitude/Longitude Location (latlng_location)

    • Input: Latitude (lat) and longitude (lng)

    • Output: Detailed address information including country, province, city, district, etc.

Development

  1. Clone the repository:

git clone https://github.com/v5tech/mcp-server-location.git
cd mcp-server-location

  1. Install dependencies:

npm install

  1. Build the project:

npm run build

  1. Development mode (watch for changes):

npm run watch

API Response Examples

  1. IP Location Response:

{
  "location": {
    "ip": "8.8.8.8",
    "coordinates": {
      "latitude": 37.751,
      "longitude": -97.822
    },
    "address": {
      "country": "United States",
      "province": "Kansas",
      "city": "Wichita",
      "district": "",
      "adcode": "US"
    }
  }
}

  1. Latitude/Longitude Location Response:

{
  "location": {
    "coordinates": {
      "latitude": 39.9042,
      "longitude": 116.4074
    },
    "address": {
      "country": "China",
      "province": "Beijing",
      "city": "Beijing",
      "district": "Dongcheng",
      "detail": "Tiananmen Square",
      "areaName": "Dongcheng District"
    }
  }
}

License

This project is licensed under the MIT License - see the LICENSE file for details.

Issues

If you encounter any problems while using this project, please feel free to submit them on the GitHub Issues page.

Available Tools

2 tools
ip_locationB

根据IP地址查询位置信息

ParametersJSON Schema
NameRequiredDescriptionDefault
ipYes要查询的IP地址

TDQS

B3.3/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description must carry behavioral disclosure. It only states the tool queries location, without mentioning whether it is read-only, requires authentication, or has any side effects. The implicit read-only nature is plausible but not stated.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single short sentence with no redundant words. It is appropriately concise for a simple tool with one parameter.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness3/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the absence of an output schema, the description does not describe the return format (e.g., city, country, coordinates). For a location lookup tool, this omission leaves some uncertainty about the response structure.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema coverage is 100% and the parameter 'ip' is described in the schema as 'IP address to query'. The description adds slight context by restating the purpose, but does not add new information beyond what the schema provides.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the action ('query') and resource ('location information') with a specific method ('based on IP address'). It effectively distinguishes from the sibling tool 'latlng_location' which likely queries by coordinates.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives, nor does it mention usage contexts or exclusions. The agent must infer usage from the tool name alone.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

latlng_locationC

根据经纬度查询位置信息

ParametersJSON Schema
NameRequiredDescriptionDefault
latYes纬度
lngYes经度

TDQS

C2.9/5.0
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description should disclose behavioral traits. It only states 'query location information' without specifying output format, error handling, or any side effects. Insufficient for a tool with no annotations.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is a single short sentence, which is concise and front-loaded. It could be more informative but is not overly verbose.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has 2 parameters, no output schema, and no annotations, the description should provide more context about the returned location information. It is too sparse to be complete.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Input schema descriptions cover 100% of parameters ('lat' and 'lng'). The description adds no extra meaning beyond the schema, so baseline score of 3 is appropriate.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: querying location information based on latitude and longitude. It uses a specific verb-resource structure, but does not differentiate from the sibling tool ip_location.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

No guidance is provided on when to use this tool versus ip_location, nor any context about prerequisites or exclusions. The description lacks usage guidelines entirely.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 2 tool updatesv1.0.0
    • First observedip_location
    • First observedlatlng_location
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A3.5/5.0
Disambiguation5/5

The tools are clearly distinct: one queries location by IP address, the other by latitude/longitude. There is no overlap in purpose or input type.

Naming Consistency5/5

Both tools follow a consistent 'input_location' pattern in snake_case, making the naming predictable and easy to understand.

Tool Count5/5

Two tools is appropriate for a focused location query server; each tool serves a unique and essential purpose without superfluous additions.

Completeness4/5

The server covers the two most common location lookups (IP geolocation and reverse geocoding). Missing forward geocoding (address to coordinates) is a minor gap but acceptable for a basic location server.

Maintenance

ActivityInactive
ResponsivenessSyncing

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • AMap Maps MCP Server

    masx200
    A
    license
    A
    quality
    C
    maintenance
    Enables location-based services through AMap/AutoNavi Maps API including geocoding, weather information, route planning, and POI searches. Supports multiple transportation modes and provides detailed geographic data for Chinese locations.
    12
    3
    Mulan Permissive Software , Version 2

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/v5tech/mcp-server-location'

If you have feedback or need assistance with the MCP directory API, please join our Discord server