MCP Datagovmy

🚀 Malaysia Open Data MCP

An MCP (Model Context Protocol) server for Malaysia's Open Data APIs, offering seamless access to government datasets and collections.

🚀 Quick Start

This MCP server enables easy access to Malaysia's open - data resources. Before you begin, 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:
  • Utilizes flexible tokenization and synonym expansion.
  • Handles queries intelligently with term normalization.
  • Supports plurals and common prefixes (e.g., "e" in "epayment").
  • Prioritizes different data types smartly.
• Parquet File Support:
  • Parses Parquet files directly in the browser or Node.js using pure JavaScript.
  • Supports BROTLI compression.
  • Falls back to metadata estimation when parsing fails.
  • Automatically maps dashboard URLs for visualization.
• Hybrid Data Access Architecture:
  • Employs pre - generated static indexes for efficient searching.
  • Makes dynamic API calls for detailed metadata.
• Multi - Provider Geocoding:
  • Supports Google Maps, GrabMaps, and Nominatim (OpenStreetMap).
  • Selects services intelligently based on location and available API keys.
  • Optimizes for locations in Malaysia with GrabMaps.
  • Automatically falls back between providers.
• Comprehensive Data Sources:
  • Offers Malaysia's Data Catalogue with rich metadata.
  • Provides interactive dashboards for data visualization.
  • Includes data from the Department of Statistics Malaysia (DOSM).
  • Offers weather forecast and warnings.
  • Provides public transport and GTFS data.
• Multi - Provider Malaysian Geocoding:
  • Optimized for Malaysian addresses and locations.
  • Features a three - tier geocoding system: GrabMaps, Google Maps, and Nominatim.
  • Prioritizes GrabMaps for better Malaysian coverage.
  • Automatically falls back to Nominatim when no API keys are provided.

🔧 Technical Details

This MCP server implements a hybrid approach for efficient data access:

• Pre - generated Static Indexes: Used for listing and searching datasets and dashboards.
• Dynamic API Calls: Made only when specific dataset or dashboard details are requested.

This approach offers 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: Contains detailed information about available tools and best practices.
• PROMPT.md: Provides AI integration guidelines and usage patterns.

💻 Usage Examples

Get Weather Forecast

const result = await tools.get_weather_forecast({
  location: "Kuala Lumpur",
  days: 3
});

Search Datasets

const result = await tools.search_datasets({
  query: "population",
  limit: 5
});

Parse GTFS Data

// Parse GTFS Static data
const staticData = await tools.parse_gtfs_static({
  provider: "ktmb"
});

// Get real - time vehicle positions
const realtimeData = await tools.parse_gtfs_realtime({
  provider: "prasarana",
  category: "rapid - rail - kl"
});

// Get transit routes
const routes = await tools.get_transit_routes({
  provider: "mybas - johor"
});

// Get stops for a specific route
const stops = await tools.get_transit_stops({
  provider: "prasarana",
  category: "rapid - rail - kl",
  route_id: "LRT - KJ"
});

📦 Installation

npm install

Development

To run the MCP server in development mode:

npx @smithery/cli dev

Build

To build the MCP server for deployment:

npx @smithery/cli build

Deployment

This MCP is designed to be deployed to Smithery. Follow these steps to deploy:

1. Make sure you have the Smithery CLI installed:

   npm install -g @smithery/cli
   

2. Build the project:

   npx @smithery/cli build
   

3. Deploy to Smithery:

   npx @smithery/cli deploy
   

Available Tools

Data Catalogue

• list_datasets: Lists available datasets in the Data Catalogue.
• get_dataset: Gets data from a specific dataset in the Data Catalogue.
• search_datasets: Searches for datasets in the Data Catalogue.

Department of Statistics Malaysia (DOSM)

• list_dosm_datasets: Lists available datasets from DOSM.
• get_dosm_dataset: Gets data from a specific DOSM dataset.

Parquet File Handling

• parse_parquet_file: Parse and display data from a Parquet file URL.
• get_parquet_info: Get metadata and structure information about a Parquet file.
• find_dashboard_for_parquet: Find the corresponding dashboard URL for a Parquet file.

Weather

• get_weather_forecast: Gets weather forecast for Malaysia.
• get_weather_warnings: Gets current weather warnings for Malaysia.
• get_earthquake_warnings: Gets earthquake warnings for Malaysia.

Transport

• list_transport_agencies: Lists available transport agencies with GTFS data.
• get_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 provider.
• parse_gtfs_realtime: Parses GTFS Realtime data (Protocol Buffer format) for vehicle positions.
• get_transit_routes: Extracts route information from GTFS data.
• get_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.

API Rate Limits

⚠️ Important Note

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 registration.
• src/datacatalogue.tools.ts: Data Catalogue API tools.
• src/dashboards.tools.ts: Dashboard access and search tools.
• src/dosm.tools.ts: Department of Statistics Malaysia tools.
• src/unified-search.tools.ts: Enhanced unified search with tokenization and synonym expansion.
• src/parquet.tools.ts: Parquet file parsing and metadata tools.
• src/weather.tools.ts: Weather forecast and warnings tools.
• src/transport.tools.ts: Transport and GTFS data tools.
• src/gtfs.tools.ts: GTFS parsing and analysis tools.
• src/flood.tools.ts: Flood warning and monitoring tools.
• Dockerfile: Docker configuration for Smithery.
• smithery.yaml: Smithery configuration.
• package.json: Project dependencies and scripts.
• tsconfig.json: TypeScript configuration.

Local Testing

To test locally before deploying to Smithery:

# Start the development server
npm run dev

# Or build and run the production version
npm run build
npm start

# In another terminal, test the hello tool
curl -X POST http://localhost:8182/invoke/hello -H "Content-Type: application/json" -d "{}"

You can also use the Smithery CLI for local development:

# Run in development mode
npx @smithery/cli dev

# Build for production
npx @smithery/cli build

Troubleshooting

Deployment Issues

⚠️ Important Note

If you encounter deployment issues:

1. Ensure your GitHub repository is public or properly connected to Smithery.
2. Verify that your Dockerfile and smithery.yaml are in the repository root.
3. 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:

1. Through Smithery's configuration interface when connecting to the MCP server
2. 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.

1. Create a .env file in the root directory with the following content:

GOOGLE_MAPS_API_KEY=your_google_api_key_here
GRAB_MAPS_API_KEY=your_grab_api_key_here
AWS_ACCESS_KEY_ID=your_aws_access_key_for_grabmaps
AWS_SECRET_ACCESS_KEY=your_aws_secret_key_for_grabmaps
AWS_REGION=ap - southeast - 5 # Malaysia region or ap - southeast - 1 # Singapore region

2. 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:

1. Click on "Connect Malaysia Open Data MCP Server"
2. You'll see configuration options for:
   • googleMapsApiKey - Google Maps API key
   • grabMapsApiKey - GrabMaps API key
   • awsAccessKeyId - AWS access key for GrabMaps
   • awsSecretAccessKey - AWS secret key for GrabMaps
   • awsRegion - AWS region for GrabMaps (e.g. ap - southeast - 5 for Malaysia region or ap - southeast - 1 for Singapore region)
3. Enter your API keys and AWS credentials in these fields
4. Click "Get Link" to generate your connection URL

The API keys will be securely passed to the server during connection.

⚠️ Important 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 Note

These geocoding credentials are only required for the following GTFS transit tools:

• get_transit_routes - When converting location names to coordinates
• get_transit_stops - When converting location names to coordinates
• parse_gtfs_static - When geocoding is needed for stop locations

⚠️ Important Note

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.

📄 License

This project is licensed under the MIT license. 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