Bengaluru BMTC MCP Server

What is Bengaluru BMTC MCP Server?

An implementation of a Model Context Protocol (MCP) server for Bangalore Metropolitan Transport Corporation (BMTC) bus services. It provides real-time transit data—including bus locations, route information, stop details, and estimated time of arrival (ETA)—through a standardized RESTful API.

How to use Bengaluru BMTC MCP Server?

Clone the repository, install dependencies (npm install), configure a .env file with MongoDB URI and optional Redis URI, then start the server (npm start or npm run dev). A Docker Compose option is also available. Once running, the API is accessible at http://localhost:3000/api/v1 with documentation at /api-docs. Optionally seed the database with mock data using node src/scripts/seed.js.

Key features of Bengaluru BMTC MCP Server

• Real-time bus location tracking across Bengaluru
• Route information and scheduling for 2,200+ routes
• Stop details and ETA (Estimated Time of Arrival)
• GeoSpatial queries for nearby stops and buses
• Authentication and authorization via JWT
• Data caching with Redis for performance optimization

Use cases of Bengaluru BMTC MCP Server

• Build real-time bus tracking applications for commuters
• Provide route planning and schedule lookup for travelers
• Display bus arrival predictions at specific stops
• Enable users to find nearby bus stops using geolocation
• Integrate BMTC transit data into third-party mobility apps

FAQ from Bengaluru BMTC MCP Server

What are the runtime requirements?

Node.js v14 or later, MongoDB, and optionally Redis (for caching) are required. Git is needed for cloning.

How do I obtain a BMTC API key for production?

For development, the server works with mock data. For production, you must contact BMTC directly to request official API access.

Is Redis mandatory to run the server?

No, Redis is optional and used only for caching. The server will operate without it.

What authentication and transport mechanisms are used?

The API uses JWT-based authentication (token issued via POST /api/v1/auth/login) and exposes RESTful endpoints over HTTP.

How many bus routes and stops are covered?

The server supports over 2,200 bus routes and 8,400+ bus stops in Bengaluru.