Skip to main content
Glama

nagoya-bus-mcp

PyPI - Version PyPI - Python Version CI

English | 日本語

Overview

Nagoya Bus MCP is a Model Context Protocol (MCP) server that lets LLMs query Nagoya City bus information. Built with FastMCP, it exposes tools and prompts for looking up bus stops, reading timetables, and checking real-time bus approach and position information. Data is sourced from the public Nagoya City bus website.

Once connected to an MCP client such as Claude Desktop, you can ask questions like "When is the next bus from Nagoya Station?" in natural language and get answers backed by live data.

Related MCP server: Singapore Bus MCP Server

Features

The server exposes the following tools:

  • get_station_number — find a bus stop number from a stop name (with fuzzy matching).

  • get_timetable — departure timetables for every route at a bus stop, organized by day of week.

  • get_approach_for_route — real-time bus positions and latest passage times along a route.

  • get_approach_for_station — real-time approaching buses for all routes at a bus stop.

It also provides prompt templates ask_timetable and ask_bus_approach for common questions.

Example queries

Bus data is in Japanese, so queries work best in Japanese:

  • 「名古屋駅のバスの時刻表を教えて」 (What's the bus timetable at Nagoya Station?)

  • 「栄のバスの接近情報を教えて」 (Show real-time bus approach info at Sakae.)

  • 「新栄町のバス停番号を教えて」 (What's the bus stop number for Shin-sakaemachi?)

Getting started

The Nagoya Bus MCP server is published to PyPI.

Claude Desktop

Add the following configuration to claude_desktop_config.json.

{
  "mcpServers": {
    "nagoya-bus": {
      "command": "uvx",
      "args": ["nagoya-bus-mcp"]
    }
  }
}

Visual Studio Code

Add the following configuration to .vscode/mcp.json.

{
  "servers": {
    "nagoya-bus": {
      "type": "stdio",
      "command": "uvx",
      "args": ["nagoya-bus-mcp"],
      "env": {}
    }
  }
}

Manual

# Using uvx
$ uvx nagoya-bus-mcp

# Using Docker
$ docker run -i --rm ghcr.io/ymyzk/nagoya-bus-mcp

For developers

# Use MCP Inspector
$ npx @modelcontextprotocol/inspector uv run nagoya-bus-mcp

# Try API client
$ uv run python -m nagoya_bus_mcp.client

Data source

This project queries the public Nagoya City bus website (https://www.kotsu.city.nagoya.jp). It is an unofficial project and is not affiliated with or endorsed by the City of Nagoya.

Available Tools

4 tools
get_approach_for_routeA

Get real-time bus approach and position information for a route.

Provides both historical data (latest bus passages at stops) and current position data for buses actively running on the route.

Inputs: route_code (required). Returns: Real-time approach information for a specific route. Contains the latest bus pa…

get_approach_for_stationA

Get real-time bus approach information for all routes at a station.

Provides a list of routes that currently have activity at the specified station (either a recent passage time or at least one approaching bus), along with a URL for more details.

Routes that have neither a latest pass time nor any approaching buses are filtered out and are not included in the result. The remaining routes are sorted by the proximity of their approaching buses so that routes with the nearest approaching vehicles appear first.

Inputs: station_number (required). Returns: Real-time approach information for a specific station. Contains the latest bus…

get_station_numberA

Get station number for a given station name using fuzzy matching.

Attempts exact match first, then falls back to fuzzy matching with 60% similarity threshold if no exact match is found.

Inputs: station_name (required). Returns: Response model for station number lookup by name. Used by the get_station_numbe…

get_timetableB

Get formatted timetable information for all routes at a station.

Retrieves and formats timetable data including routes, directions, boarding locations, and departure times organized by day of week.

Inputs: station_number (required). Returns: Response model for station timetable queries. Contains all timetables for diffe…

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.8/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool targets a distinct operation: route-level approach, station-level approach, station number lookup, and timetable retrieval. No overlap in purpose.

    Naming Consistency5/5

    All tools follow a consistent 'get_X_for_Y' pattern with clear verb_noun structure, using snake_case throughout.

    Tool Count4/5

    4 tools is slightly low but acceptable for a focused bus information server. Each tool serves a clear purpose without being redundant.

    Completeness3/5

    Missing tools to list available routes or stations, which may create dead ends for agents that don't know route or station names in advance. Core real-time and timetable queries are covered.

    Maintenance

    ActivityMaintained
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers