MCP.so
Sign In

MCP Servers Collection

@asterism45

Basic information

Category

Other

Transports

stdio

Author

asterism45

About MCP Servers Collection

No overview available yet

MCP Servers Collection config

No standard config provided

This server doesn't expose a parseable MCP config block in its README. See the repository for install instructions.

Repository

MCP Servers Collection tools

Tool list not available yet

This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.

We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.

Overview

What is MCP Servers Collection?

A collection of Model Context Protocol (MCP) servers that enable language models like Claude to access real‑time data and functionalities from external services, including transit routes, driving directions, and place information.

How to use MCP Servers Collection?

Clone the repository, navigate to a server directory (e.g., navitime-transit-server), install dependencies with npm install, build with npm run build, then add the server’s build entry (e.g., build/index.js) to your Claude Desktop configuration file (claude_desktop_config.json) under the mcpServers object.

Key features of MCP Servers Collection

  • Provides transit route information via the Navitime API.
  • Offers driving, walking, and cycling directions using Google Maps Directions API.
  • Returns place details (address, phone, ratings, reviews) via the Google Places API.
  • Each server is a separate Node.js (TypeScript) project with standard build scripts.
  • Easily integrated with Claude Desktop through claude_desktop_config.json.
  • Debugging supported via the MCP Inspector.

Use cases of MCP Servers Collection

  • Querying train schedules, fares, and transfer information from Navitime.
  • Getting point‑to‑point directions for driving, walking, or cycling.
  • Looking up addresses, phone numbers, ratings, and reviews of places.

Frequently asked questions

1

What API keys are required?

The `googlemaps-directions-server` requires a valid Google Maps API key; the `places-server` requires a valid Google Places API key. The `navitime-transit-server` uses the Navitime API (key details in its own README).

2

How do I configure a server in Claude Desktop?

Edit `claude_desktop_config.json` (macOS: `~/Library/Application Support/Claude/Claude/claude_desktop_config.json`; Windows: `%APPDATA%/Claude/claude_desktop_config.json`) and add an entry under `mcpServers` with the absolute path to the server’s built JavaScript file.

3

What are the runtime requirements?

Each server is a Node.js (TypeScript) project; Node.js is required. Build steps: `npm install` then `npm run build`.

4

How can I debug an MCP server?

Use the MCP Inspector. From the server directory, run `npm run inspector` (if defined in `package.json`) to open a debugging URL.

5

Where does the data come from?

Data comes from the respective external APIs: Navitime API for transit, Google Maps Directions API for directions, and Google Places API for place information.

Comments

More Other MCP servers