This MCP server provides seamless access to Malaysia's government open data, including datasets, w…
Glama MCP Gateway
Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.
Full call logging
Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.
Tool access control
Enable or disable individual tools per connector, so you decide what your agents can and cannot do.
Managed credentials
Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.
Usage analytics
See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.
Average 3.3/5 across 31 of 31 tools scored. Lowest: 2.5/5.
There is significant overlap between tools, especially in search and transit functions, which could cause confusion. For example, search_all, search_dashboards, and search_datasets_catalogue have overlapping purposes, and tools like get_transit_routes and parse_gtfs_static serve similar functions. However, descriptions provide some guidance to differentiate them.
All tool names follow a consistent snake_case pattern with a 'datagovmy_' prefix and descriptive verb_noun combinations. The naming is highly predictable and uniform across all 31 tools, making it easy to understand their purposes at a glance.
With 31 tools, the count feels excessive for the domain of Malaysian open data access. Many tools could be consolidated, such as the multiple search and transit-related tools, leading to a bloated interface that may overwhelm agents and increase misselection risk.
The tool set covers a wide range of data types, including datasets, dashboards, transit, weather, and warnings, with good CRUD-like operations for filtering and retrieving data. Minor gaps exist, such as limited update or delete capabilities, but these are typical for read-heavy data platforms, and agents can work around them effectively.
Claim this connector by publishing a /.well-known/glama.json file on your server's domain with the following structure:
{
"$schema": "https://glama.ai/mcp/schemas/connector.json",
"maintainers": [{ "email": "your-email@example.com" }]
}The email address must match the email associated with your Glama account. Once published, Glama will automatically detect and verify the file within a few minutes.
Control your server's listing on Glama, including description and metadata
Access analytics and receive server usage reports
Get monitoring and health status updates for your server
Feature your server to boost visibility and reach more users
For users:
Full audit trail – every tool call is logged with inputs and outputs for compliance and debugging
Granular tool control – enable or disable individual tools per connector to limit what your AI agents can do
Centralized credential management – store and rotate API keys and OAuth tokens in one place
Change alerts – get notified when a connector changes its schema, adds or removes tools, or updates tool definitions, so nothing breaks silently
For server owners:
Proven adoption – public usage metrics on your listing show real-world traction and build trust with prospective users
Tool-level analytics – see which tools are being used most, helping you prioritize development and documentation
Direct user feedback – users can report issues and suggest improvements through the listing, giving you a channel you would not have otherwise
The connector status is unhealthy when Glama is unable to successfully connect to the server. This can happen for several reasons:
The server is experiencing an outage
The URL of the server is wrong
Credentials required to access the server are missing or invalid
If you are the owner of this MCP connector and would like to make modifications to the listing, including providing test credentials for accessing the server, please contact support@glama.ai.
No comments yet. Be the first to start the discussion!
Sign in to create a connector for this server.