Provides Docker configuration for deployment to Smithery platform
Used to load environment variables from a .env file during development for storing API keys and configuration
Mentions GitHub repository access for deployment purposes
Provides geocoding services for Malaysian locations, used particularly for GTFS transit features to convert location names to coordinates
Utilizes GrabMaps API for optimized geocoding of Malaysian addresses and locations, offering better accuracy than other providers for Malaysian locations
Enables Parquet file parsing directly in Node.js environments, supporting BROTLI compression and metadata estimation
Uses Nominatim (OpenStreetMap) as a fallback geocoding service when Google Maps or GrabMaps API keys are not provided
Uses TypeScript for the MCP server implementation with configuration available in the project structure
Malaysia Open Data MCP
MCP (Model Context Protocol) server for Malaysia's Open Data APIs, providing easy access to government datasets and collections.
Do note that this is NOT an official MCP server by the Government of Malaysia or anyone from Malaysia's Open Data/Jabatan Digital Negara/Ministry of Digital team.
Features
- Enhanced Unified Search with flexible tokenization and synonym expansion
- Intelligent query handling with term normalization
- Support for plurals and common prefixes (e.g., "e" in "epayment")
- Smart prioritization for different data types
- Parquet File Support using pure JavaScript
- Parse Parquet files directly in the browser or Node.js
- Support for BROTLI compression
- Fallback to metadata estimation when parsing fails
- Automatic dashboard URL mapping for visualization
- Hybrid Data Access Architecture
- Pre-generated static indexes for efficient searching
- Dynamic API calls for detailed metadata
- Multi-Provider Geocoding
- Support for Google Maps, GrabMaps, and Nominatim (OpenStreetMap)
- Intelligent service selection based on location and available API keys
- GrabMaps optimization for locations in Malaysia
- Automatic fallback between providers
- Comprehensive Data Sources
- Malaysia's Data Catalogue with rich metadata
- Interactive Dashboards for data visualization
- Department of Statistics Malaysia (DOSM) data
- Weather forecast and warnings
- Public transport and GTFS data
- Multi-Provider Malaysian Geocoding
- Optimized for Malaysian addresses and locations
- Three-tier geocoding system: GrabMaps, Google Maps, and Nominatim
- Prioritizes local knowledge with GrabMaps for better Malaysian coverage
- Automatic fallback to Nominatim when no API keys are provided
Architecture
This MCP server implements a hybrid approach for efficient data access:
- Pre-generated Static Indexes for listing and searching datasets and dashboards
- Dynamic API Calls only when specific dataset or dashboard details are requested
This approach provides several benefits:
- Faster search and listing operations
- Reduced API calls to external services
- Consistent data access patterns
- Up-to-date detailed information when needed
Documentation
- TOOLS.md - Detailed information about available tools and best practices
- PROMPT.md - AI integration guidelines and usage patterns
AI Integration
When integrating this MCP server with AI models:
- Use the unified search tool first - Always start with
search_all
for any data queries - Follow the correct URL patterns - Use
https://data.gov.my/...
andhttps://open.dosm.gov.my/...
- Leverage Parquet file tools - Use
parse_parquet_file
to access data directly orget_parquet_info
for metadata - Use the hybrid approach - Static indexes for listing/searching, API calls for details
- Consider dashboard visualization - For complex data, use the dashboard links provided by
find_dashboard_for_parquet
- Leverage the multi-provider Malaysian geocoding - For Malaysian location queries, the system automatically selects the best provider (GrabMaps, Google Maps, or Nominatim) with fallback to Nominatim when no API keys are configured
Refer to PROMPT.md for comprehensive AI integration guidelines.
Installation
Development
To run the MCP server in development mode:
Build
To build the MCP server for deployment:
Deployment
This MCP is designed to be deployed to Smithery. Follow these steps to deploy:
- Make sure you have the Smithery CLI installed:
- Build the project:
- Deploy to Smithery:
Available Tools
Data Catalogue
list_datasets
: Lists available datasets in the Data Catalogueget_dataset
: Gets data from a specific dataset in the Data Cataloguesearch_datasets
: Searches for datasets in the Data Catalogue
Department of Statistics Malaysia (DOSM)
list_dosm_datasets
: Lists available datasets from DOSMget_dosm_dataset
: Gets data from a specific DOSM dataset
Parquet File Handling
parse_parquet_file
: Parse and display data from a Parquet file URLget_parquet_info
: Get metadata and structure information about a Parquet filefind_dashboard_for_parquet
: Find the corresponding dashboard URL for a Parquet file
Weather
get_weather_forecast
: Gets weather forecast for Malaysiaget_weather_warnings
: Gets current weather warnings for Malaysiaget_earthquake_warnings
: Gets earthquake warnings for Malaysia
Transport
list_transport_agencies
: Lists available transport agencies with GTFS dataget_transport_data
: Gets GTFS data for a specific transport agency
GTFS Parsing
parse_gtfs_static
: Parses GTFS Static data (ZIP files with CSV data) for a specific transport providerparse_gtfs_realtime
: Parses GTFS Realtime data (Protocol Buffer format) for vehicle positionsget_transit_routes
: Extracts route information from GTFS dataget_transit_stops
: Extracts stop information from GTFS data, optionally filtered by route
Test
hello
: A simple test tool to verify that the MCP server is working correctly
Usage Examples
Get Weather Forecast
Search Datasets
Parse GTFS Data
API Rate Limits
Please be aware of rate limits for the underlying APIs. Excessive requests may be throttled.
Project Structure
src/index.ts
: Main MCP server implementation and tool registrationsrc/datacatalogue.tools.ts
: Data Catalogue API toolssrc/dashboards.tools.ts
: Dashboard access and search toolssrc/dosm.tools.ts
: Department of Statistics Malaysia toolssrc/unified-search.tools.ts
: Enhanced unified search with tokenization and synonym expansionsrc/parquet.tools.ts
: Parquet file parsing and metadata toolssrc/weather.tools.ts
: Weather forecast and warnings toolssrc/transport.tools.ts
: Transport and GTFS data toolssrc/gtfs.tools.ts
: GTFS parsing and analysis toolssrc/flood.tools.ts
: Flood warning and monitoring toolsDockerfile
: Docker configuration for Smitherysmithery.yaml
: Smithery configurationpackage.json
: Project dependencies and scriptstsconfig.json
: TypeScript configuration
Local Testing
To test locally before deploying to Smithery:
You can also use the Smithery CLI for local development:
Troubleshooting
Deployment Issues
If you encounter deployment issues:
- Ensure your GitHub repository is public or properly connected to Smithery
- Verify that your
Dockerfile
andsmithery.yaml
are in the repository root - Check that the
index.js
file exports a valid MCP server function
Configuration
Environment Variables
This project supports the following configuration options:
Geocoding Credentials (Optional. Only for GTFS Transit Features Usage):
The following credentials are only needed if you plan to use the GTFS transit tools that require geocoding services. Other features like data catalogue access, weather forecasts, and DOSM data do not require these credentials.
- googleMapsApiKey: Optional. If provided, the system will use Google Maps API for geocoding location names to coordinates.
- grabMapsApiKey: Optional. Required for GrabMaps geocoding, which is optimized for locations in Malaysia.
- awsAccessKeyId: Required for GrabMaps integration. AWS access key for GrabMaps API authentication.
- awsSecretAccessKey: Required for GrabMaps integration. AWS secret key for GrabMaps API authentication.
- awsRegion: Required for GrabMaps integration. AWS region for GrabMaps API (e.g. 'ap-southeast-5' for Malaysia region or ap-southeast-1 for Singapore region).
If neither Google Maps nor GrabMaps API keys are provided, the GTFS transit tools will automatically fall back to using Nominatim (OpenStreetMap) API for geocoding, which is free and doesn't require credentials.
You can set these configuration options in two ways:
- Through Smithery's configuration interface when connecting to the MCP server
- As environment variables (GOOGLE_MAPS_API_KEY, GRAB_MAPS_API_KEY) for local development
Setting up environment variables
For local development:
The project uses dotenv
to load environment variables from a .env
file during development.
- Create a
.env
file in the root directory with the following content:
- The variables will be automatically loaded when you run the server locally using
npm run dev
For Smithery deployment:
When connecting to your MCP server through Smithery:
- Click on "Connect Malaysia Open Data MCP Server"
- You'll see configuration options for:
googleMapsApiKey
- Google Maps API keygrabMapsApiKey
- GrabMaps API keyawsAccessKeyId
- AWS access key for GrabMapsawsSecretAccessKey
- AWS secret key for GrabMapsawsRegion
- AWS region for GrabMaps (e.g. ap-southeast-5 for Malaysia region or ap-southeast-1 for Singapore region)
- Enter your API keys and AWS credentials in these fields
- Click "Get Link" to generate your connection URL
The API keys will be securely passed to the server during connection.
Note: For Malaysian locations, GrabMaps provides the most accurate geocoding results, followed by Google Maps, with both requiring API keys. If you don't provide either API key, the system will automatically use Nominatim API instead, which is free but may have less accurate results for some locations in Malaysia.
Important: These geocoding credentials are only required for the following GTFS transit tools:
get_transit_routes
- When converting location names to coordinatesget_transit_stops
- When converting location names to coordinatesparse_gtfs_static
- When geocoding is needed for stop locations
Note about GTFS Realtime Tools: The parse_gtfs_realtime
tool is currently in development and has limited availability. Real-time data access through this MCP is experimental and may not be available for all providers or routes. For up-to-date train and bus schedules, bus locations, and arrivals in real-time, please use official transit apps like Google Maps, MyRapid PULSE, Moovit, or Lugo.
All other tools like data catalogue access, dashboard search, weather forecasts, and DOSM data do not require any geocoding credentials.
License
MIT - See LICENSE file for details.
Acknowledgments
- Malaysia Open Data Portal
- Department of Statistics Malaysia
- Malaysian Meteorological Department
- Google Maps Platform for geocoding
- GrabMaps for geocoding
- Nominatim for geocoding
- Smithery for the MCP framework
This server cannot be installed
remote-capable server
The server can be hosted and run remotely because it primarily relies on remote services or has no dependency on the local environment.
MCP server providing access to Malaysia's government datasets, dashboards, weather forecasts, and transport data through a unified search system and hybrid data access architecture.
Related MCP Servers
- AsecurityAlicenseAqualityModel Context Protocol (MCP) server that provides weather forecast, warnings, water level associated with flood, and earthquake reports from Malaysia Government's Open API.Last updated -41PythonMIT License
- -securityFlicense-qualityAn MCP server implementation that allows users to fetch and display weather information for specified cities, including temperature, humidity, wind speed, and weather descriptions.Last updated -1Python
- -securityAlicense-qualityAn MCP server that connects to OpenWeatherMap's API to provide current weather data and multi-day forecasts for locations worldwide in different measurement units.Last updated -23TypeScriptMIT License
- AsecurityFlicenseAqualityMCP server that provides Korean weather information using grid coordinates and the Korea Meteorological Administration API, allowing users to query current weather conditions and forecasts for specific locations in Korea.Last updated -23Python