If you are building Model Context Protocol servers --- for agents, IDEs, AI tools --- and you need clean Australian government data inside the tools you ship, ausdata.io is built for you.
We maintain 9 sister MCP servers covering Australia main public data sources, plus a hosted REST API behind them. All sisters are open source on PyPI. Use them directly, fork them, contribute back.
The 9 sister MCP servers
Package Source Licence
abs-mcp Australian Bureau of MIT
Statistics
rba-mcp Reserve Bank of MIT
Australia
ato-mcp Australian Taxation MIT
Office
apra-mcp Australian Prudential MIT
Regulation Authority
aihw-mcp Australian Institute of MIT
Health and Welfare
asic-mcp Australian Securities MIT
and Investments
Commission
aemo-mcp Australian Energy MIT
Market Operator
wgea-mcp Workplace Gender MIT
Equality Agency
au-weather-mcp Bureau of Meteorology MIT
via Open-Meteo
Each sister exposes 5 core tools:
search_<source>(query, limit)--- fuzzy search across known datasetsdescribe_<source>(id)--- schema + filter valuesget_data(id, filters, start_period, end_period)--- querylatest(id, filters)--- current snapshotlist_curated()--- enumerate supported IDs
Two ways to use
Option 1: Direct (per-sister, pip-installed)
pip install rba-mcp
Then in your MCP host config:
{
"mcpServers": {
"rba": {
"command": "python",
"args": ["-m", "rba_mcp"]
}
}
}
Free, MIT-licensed, no API key required. Best for personal projects, hobbyist tools, open-source contributions.
Option 2: Unified hosted (one server, all 9 sources)
npx ausdata-mcp
Then in your MCP host config:
{
"mcpServers": {
"ausdata": {
"command": "npx",
"args": ["ausdata-mcp"],
"env": { "AUSDATA_API_KEY": "ak_YOUR_KEY" }
}
}
}
Plus the composer endpoints (real_rate_regime, inflation_decomposition, etc.) as additional tools. Free tier 500 calls/month. Best for production tools and AI agents.
Why choose option 1 vs option 2
Option 1 (sister MCPs directly):
- Free, no key needed
- Fork and modify each sister
- Contribute back via PR
- Best for personal projects and hobbyist tools
Option 2 (hosted unified):
- One key, one envelope, one upgrade path
- Composer endpoints (cross-source signals)
- Webhooks on dataset releases
- Caching + stale-fallback + reliability
- Best for production tools
Many MCP builders start with option 1 to evaluate, then move to option 2 when they ship to production.
Contributing back
Each sister is open source on GitHub at Bigred97/<source>-mcp. We
welcome:
- Bug fixes
- New datasets within the sister scope
- Improvements to filter mapping
- Test coverage
- Documentation improvements
For new datasets outside the existing 9 sources, open an issue first to discuss scope.
Building your own MCP using ours
If you are building a vertical MCP (e.g. "Australian financial planner copilot") and need AU public data as a subset, you have two paths:
- Import our sisters or call our hosted API directly inside your tool
- Fork the relevant sister and customise the tool surface for your use case
The MIT licence permits both. Attribution is appreciated but not required.
Why this matters for MCP builders
Three reliability issues MCP-only solutions hit without ausdata:
- Per-source maintenance burden. Building 9 sister servers from scratch is 6-12 months of work. We did that work.
- Schema drift. ABS, RBA, AEMO change their data formats periodically. We track and adapt; you inherit the stability.
- Cross-source composition. No single sister can answer "what is the current real cash rate" because that requires joining ABS + RBA. The hosted API exposes the join.
Pricing for MCP builders
- Per-sister (option 1): free forever, MIT-licensed.
- Hosted unified (option 2): free tier 500 calls/month covers most personal use. Paid tiers $29-99/mo for production.
Related
/docs/mcp--- full reference/sdk/mcp--- install instructions/cookbook--- 10 worked recipes- GitHub: Bigred97/abs-mcp, rba-mcp, ato-mcp, apra-mcp, aihw-mcp, asic-mcp, aemo-mcp, wgea-mcp, au-weather-mcp
Get a free API key → /register