Nagoya Bus

MCP server that exposes Nagoya Bus endpoints for MCP clients and tooling.

javascript

1

GitHub Stars

javascript

Language

6 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": {
    "ymyzk-nagoya-bus-mcp": {
      "command": "uvx",
      "args": [
        "nagoya-bus-mcp"
      ]
    }
  }
}

Nagoya Bus MCP server lets you expose an MCP endpoint locally or remotely so your MCP clients can connect to it. It integrates with tooling that runs on your machine or in containers, enabling you to test and develop MCP interactions efficiently.

How to use

You connect an MCP client to the Nagoya Bus MCP server by configuring the client to point at a local stdio session or to a remote HTTP endpoint if you have one. In practice, you run the Nagoya Bus MCP server locally and then start your MCP client with the appropriate connection details. When the server is running, the client will communicate commands and responses through the MCP protocol as if the server were a remote service. This setup is ideal for iterative development and testing of MCP-driven workflows.

How to install

Prerequisites vary by how you want to run the server. You can start the server using the provided runtime, or you can run it inside Docker. Choose one of the following workflows.

# Using uvx
$ uvx nagoya-bus-mcp

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

Manual configuration for client integration

If you are integrating with a GUI or desktop client, you can add the following MCP server configuration to connect to Nagoya Bus MCP via stdio:

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

For developers

If you are developing against the Nagoya Bus MCP server, you can inspect MCP activity and test the API client against the running process.

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

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