Skip to main content
Glama
BACH-AI-Tools

City By Api Ninjas MCP Server

by BACH-AI-Tools
OverviewSchemaRelated ServersScoreDiscussions
Python
Remote

City By Api Ninjas MCP Server

English | 简体中文 | 繁體中文

用于访问 City By Api Ninjas API 的 MCP 服务器。

🚀 使用 EMCP 平台快速体验

EMCP 是一个强大的 MCP 服务器管理平台，让您无需手动配置即可快速使用各种 MCP 服务器！

快速开始：

  1. 🌐 访问 EMCP 平台

  2. 📝 注册并登录账号

  3. 🎯 进入 MCP 广场，浏览所有可用的 MCP 服务器

  4. 🔍 搜索或找到本服务器（bach-city_by_api_ninjas）

  5. 🎉 点击 "安装 MCP" 按钮

  6. ✅ 完成！即可在您的应用中使用

EMCP 平台优势：

  • ✨ 零配置：无需手动编辑配置文件

  • 🎨 可视化管理：图形界面轻松管理所有 MCP 服务器

  • 🔐 安全可靠：统一管理 API 密钥和认证信息

  • 🚀 一键安装：MCP 广场提供丰富的服务器选择

  • 📊 使用统计：实时查看服务调用情况

立即访问 EMCP 平台 开始您的 MCP 之旅！

Related MCP server: Geocoding By API Ninjas

简介

这是一个 MCP 服务器，用于访问 City By Api Ninjas API。

  • PyPI 包名: bach-city_by_api_ninjas

  • 版本: 1.0.0

  • 传输协议: stdio

安装

从 PyPI 安装:

pip install bach-city_by_api_ninjas

从源码安装:

pip install -e .

运行

方式 1: 使用 uvx（推荐，无需安装）

# 运行（uvx 会自动安装并运行）
uvx --from bach-city_by_api_ninjas bach_city_by_api_ninjas

# 或指定版本
uvx --from bach-city_by_api_ninjas@latest bach_city_by_api_ninjas

方式 2: 直接运行（开发模式）

python server.py

方式 3: 安装后作为命令运行

# 安装
pip install bach-city_by_api_ninjas

# 运行（命令名使用下划线）
bach_city_by_api_ninjas

配置

API 认证

此 API 需要认证。请设置环境变量:

export API_KEY="your_api_key_here"

环境变量

变量名

说明

必需

API_KEY

API 密钥

是

PORT

不适用

否

HOST

不适用

否

在 Cursor 中使用

编辑 Cursor MCP 配置文件 ~/.cursor/mcp.json:

{
  "mcpServers": {
    "bach-city_by_api_ninjas": {
      "command": "uvx",
      "args": ["--from", "bach-city_by_api_ninjas", "bach_city_by_api_ninjas"],
      "env": {
        "API_KEY": "your_api_key_here"
      }
    }
  }
}

在 Claude Desktop 中使用

编辑 Claude Desktop 配置文件 claude_desktop_config.json:

{
  "mcpServers": {
    "bach-city_by_api_ninjas": {
      "command": "uvx",
      "args": ["--from", "bach-city_by_api_ninjas", "bach_city_by_api_ninjas"],
      "env": {
        "API_KEY": "your_api_key_here"
      }
    }
  }
}

可用工具

此服务器提供以下工具:

v1city

API Ninjas City API endpoint.

端点: GET /v1/city

参数:

  • name (string): Name of city.

  • country (string): Country filter. Must be an ISO-3166 alpha-2 code (e.g. US).

  • min_population (number): Minimum city population.

  • max_population (number): Maximum city population.

  • min_lat (number): Minimum latitude coordinate.

  • max_lat (number): Maximum latitude coordinate.

  • min_lon (number): Minimum longitude coordinate.

  • max_lon (number): Maximum longitude coordinate.

  • limit (number): How many results to return. Must be between 1 and 30. Default is 1.

技术栈

  • 传输协议: stdio

  • HTTP 客户端: httpx

许可证

MIT License - 详见 LICENSE 文件。

开发

此服务器由 API-to-MCP 工具生成。

版本: 1.0.0

Available Tools

1 tool
v1cityD

API Ninjas City API endpoint.

ParametersJSON Schema
NameRequiredDescriptionDefault
nameNoName of city.
countryNoCountry filter. Must be an ISO-3166 alpha-2 code (e.g. US).
min_populationNoMinimum city population.0
max_populationNoMaximum city population.0
min_latNoMinimum latitude coordinate.0
max_latNoMaximum latitude coordinate.0
min_lonNoMinimum longitude coordinate.0
max_lonNoMaximum longitude coordinate.0
limitNoHow many results to return. Must be between 1 and 30. Default is 1.1

TDQS

D1.7/5.0
Behavior1/5

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

With no annotations provided, the description carries the full burden of disclosing behavioral traits, yet it reveals nothing about whether this is a read-only query, what data structure it returns, pagination behavior, or error conditions. The agent cannot determine if this is a safe operation or what side effects might occur.

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

Conciseness2/5

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

While the description is brief (5 words), it represents under-specification rather than efficient conciseness. The single sentence fails to earn its place by providing actionable information about the tool's functionality, wasting the opportunity to guide the agent.

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

Completeness1/5

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

For a tool with 9 parameters and no output schema or annotations, the description is woefully incomplete. It fails to explain the query logic (how filters combine), the return format, or the relationship to the API Ninjas service, leaving critical gaps in the agent's understanding.

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?

The input schema has 100% description coverage, documenting all 9 parameters (name, country, population ranges, coordinates, limit) adequately. The description adds no parameter-specific context, but the high schema coverage establishes a baseline score of 3 as per the evaluation guidelines.

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

Purpose2/5

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

The description 'API Ninjas City API endpoint' is tautological, restating the tool's category without specifying what action it performs (e.g., search, retrieve, list). While it identifies the external service provider (API Ninjas), it lacks a specific verb or clear statement of what the tool does with city data.

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

Usage Guidelines1/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 prerequisites such as API keys, rate limits, or required parameter combinations. With no sibling tools to differentiate from, this represents a complete absence of usage guidance.

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

Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

C2.2/5.0
Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools. The tool 'v1city' stands alone with a clear purpose, so agents cannot misselect between multiple options.

Naming Consistency5/5

A single tool inherently has consistent naming, as there are no other tools to compare it against. The name 'v1city' follows a pattern that includes versioning and the resource, which is straightforward and predictable in isolation.

Tool Count2/5

One tool is too few for a server named 'City By Api Ninjas MCP Server', which suggests a domain focused on city-related data. A single endpoint limits functionality and feels thin, as typical city APIs might include operations like search, get details, or list cities, not just one endpoint.

Completeness2/5

The server's purpose implies city data operations, but with only one tool ('v1city'), the surface is severely incomplete. There are obvious gaps, such as missing CRUD operations or specific queries, which will likely cause agent failures when trying to perform comprehensive city-related tasks.

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

  • Weather By Api Ninjas

    BACH-AI-Tools
    A
    license
    C
    quality
    D
    maintenance
    Provides access to weather information by location using the API Ninjas Weather API, supporting queries by coordinates, zip code, city, state, and country.
    1
    MIT

  • Country By Api Ninjas MCP

    BACH-AI-Tools
    A
    license
    C
    quality
    D
    maintenance
    Provides access to the API Ninjas Country API, allowing users to query detailed country data including GDP, population, area, and other demographic metrics. It enables filtering countries by specific economic and geographic criteria through natural language commands.
    1
    MIT

  • Geodb Cities MCP Server

    BACH-AI-Tools
    A
    license
    B
    quality
    C
    maintenance
    Provides access to the GeoDB Cities API for retrieving global geographic data including city details, populations, and local time. It enables users to find nearby locations, calculate distances between places, and browse administrative divisions across countries.
    18
    MIT

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/BACH-AI-Tools/city_by_api_ninjas'

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