Install Demiton MCP
Add Demiton to Claude Desktop, Cursor, or any client that speaks the Model Context Protocol. Once installed, Claude can query every public dataset in the Civil Pipeline Digest - and your own uploaded contracts if you sign in to Insights - with a source trace attached to every answer.
Open your MCP client config
Demiton works with any MCP-compatible client. The most common setups:
- Claude Desktop - open
claude_desktop_config.json(Settings → Developer → Edit Config). - Cursor - open
~/.cursor/mcp.jsonor the project-local.cursor/mcp.json. - Other MCP clients - see modelcontextprotocol.io/clients.
Paste the Demiton server config
For Claude Desktop:
{
"mcpServers": {
"demiton": {
"url": "https://api.demiton.io/mcp",
"transport": "http"
}
}
}For Cursor:
{
"mcpServers": {
"demiton": {
"url": "https://api.demiton.io/mcp"
}
}
}That's it - no API key, no secret, no install script. The Demiton MCP server is a remote HTTP endpoint at https://api.demiton.io/mcp.
Restart your client and start asking
Restart Claude Desktop or reload Cursor's MCP servers. You should see demiton appear in the connected-tools list. Try one of these prompts:
- > Which Defence S-EST tenders are open right now and when do they close?
- > What was the most recent RBA cash rate decision and what is the current target?
- > Which contractors have won the most TMR work in FY 2025-26 so far?
- > What's the BOM 7-day forecast for Brisbane and is it suitable for open earthworks?
- > Look up ABN 54000538689 against the Australian Business Register and confirm trading status.
Two access tiers
AusTender ATMs and awards, RBA Statistics, ABS Data API, BOM weather, the Australian Business Register, and tracked open-data datasets (TMR Works to Tender, TMR Contract Disclosure, QTRIP). Rate-limited.
Upload your contract history. Claude can then cross-reference your schedule rates against TMR and AusTender awards, and surface margin drift on a per-job basis. OAuth 2.1 secured.
Start a trialEvery figure Claude returns from Demiton has a verifiable trace back to its source connector, API call, and timestamp. No black-box summaries - the citation graph is part of the response.