Victorian Council Bin Lookup
Local MCP server for checking council bin collection dates from a residential address.
README
Victorian Council Bin Lookup
Victorian Council Bin Lookup is a local MCP server for checking council bin collection dates from a residential address.
It exposes a get_bin_collection MCP tool that returns upcoming rubbish, recycling, and food/garden collection dates in a structured format.
The server is designed to grow council-by-council, using small adapters for each council's public lookup system.
Supported Councils
- City of Casey
- Hume City Council
Features
- Look up bin collection dates by address
- Supports City of Casey and Hume City Council
- Returns structured MCP output for AI agents
- Handles council-specific address formatting
- No OpenAI API key required
- Runs locally over MCP stdio or remotely over HTTP
Install
Clone this repository and install dependencies:
git clone https://github.com/williamyun7/victorian-council-bin-lookup.git
cd victorian-council-bin-lookup
npm install
This project currently has no external npm dependencies, but npm install will still prepare the local package if dependencies are added later.
Test Directly
npm run test:call
You can pass an address and council:
npm run test:call -- --council casey 123 Demo Street Exampleville 3999
npm run test:call -- --council hume 45 Sample Road Testfield 3998
Add to Codex
codex mcp add victorian-council-bin-lookup -- node /path/to/victorian-council-bin-lookup/server.js
Then start a new Codex thread and ask:
Use the Victorian Council Bin Lookup MCP tool to check which bins are collected for 123 Demo Street Exampleville this week.
The server exposes one MCP tool: get_bin_collection.
Run as an HTTP Server
For Azure or other hosted environments, run the HTTP entrypoint:
npm start
By default this listens on port 3000. You can change it with PORT:
PORT=8080 npm run http
HTTP endpoints:
GET /healthhealth check for hosting platformsPOST /mcpJSON-RPC MCP endpointGET /api/bin-collection?address=...&council=autosimple REST endpoint for testing
Optional environment variables:
API_KEYprotects/mcpand/api/bin-collectionwithAuthorization: Bearer <key>orx-api-key: <key>ALLOWED_ORIGINScomma-separated list of allowed browser originsPORTHTTP listen portHOSTHTTP bind host, defaults to0.0.0.0for container hosting
Example REST test:
curl "http://localhost:3000/api/bin-collection?address=123%20Demo%20Street%20Exampleville%203999&council=casey"
Example MCP initialize call:
curl -X POST "http://localhost:3000/mcp" \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"curl","version":"1.0.0"}}}'
Deploy to Azure App Service
Azure App Service is the recommended Azure deployment path for this project. It avoids Azure Container Registry build tasks and runs the HTTP MCP endpoint with npm start.
az login
az group create \
--name victorian-council-bin-lookup-rg \
--location australiaeast \
--output table
az appservice plan create \
--name victorian-council-bin-lookup-plan \
--resource-group victorian-council-bin-lookup-rg \
--location australiaeast \
--sku F1 \
--is-linux \
--output table
az webapp create \
--name victorian-council-bin-lookup \
--resource-group victorian-council-bin-lookup-rg \
--plan victorian-council-bin-lookup-plan \
--runtime "NODE:22-lts" \
--startup-file "npm start" \
--output table
Deploy from the repository folder:
zip -r app.zip . -x ".git/*" "node_modules/*" "app.zip"
az webapp deploy \
--name victorian-council-bin-lookup \
--resource-group victorian-council-bin-lookup-rg \
--src-path app.zip \
--type zip
Test the deployed app:
curl https://victorian-council-bin-lookup.azurewebsites.net/health
Expected response:
{"ok":true,"service":"victorian-council-bin-lookup"}
Test the MCP endpoint:
curl -X POST "https://victorian-council-bin-lookup.azurewebsites.net/mcp" \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'
To require an API key:
az webapp config appsettings set \
--name victorian-council-bin-lookup \
--resource-group victorian-council-bin-lookup-rg \
--settings API_KEY="replace-with-a-long-random-value"
Then include the key when calling /mcp or /api/bin-collection:
curl -X POST "https://victorian-council-bin-lookup.azurewebsites.net/mcp" \
-H "Content-Type: application/json" \
-H "Authorization: Bearer replace-with-a-long-random-value" \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/list","params":{}}'
The App Service deployment runs npm start, which starts http-server.js.
Deploy to Azure Container Apps
The included Dockerfile can also run this server on Azure Container Apps, but az containerapp up --source . uses Azure Container Registry Tasks to build the image. Some subscriptions do not allow ACR Tasks and will fail with TasksOperationsNotAllowed.
If your subscription supports ACR Tasks, deploy from the repository folder:
az extension add --name containerapp --upgrade
az provider register --namespace Microsoft.App
az provider register --namespace Microsoft.OperationalInsights
az provider register --namespace Microsoft.ContainerRegistry
az containerapp up \
--name victorian-council-bin-lookup \
--resource-group victorian-council-bin-lookup-rg \
--location australiaeast \
--environment victorian-council-bin-lookup-env \
--source .
Tool Input
get_bin_collection accepts:
addressrequired residential addresscounciloptional value:auto,casey, orhumedateoptional date inYYYY-MM-DDformat, defaulting to today in Melbourne time
Address input is formatted for each council before lookup.
- Casey searches uppercase addresses and keeps/adds
VICbefore a postcode, for example123 DEMO STREET EXAMPLEVILLE VIC 3999. - Hume removes
VICand tidies comma spacing, for example45 Sample Road, Testfield 3998.
Example Prompts
Use the Victorian Council Bin Lookup MCP tool to check which bins are collected for 123 Demo Street Exampleville VIC 3999 this week.
Use the Victorian Council Bin Lookup MCP tool to check the bin collection for 45 Sample Road, Testfield 3998 next week.
Responsible Use
This project uses public council lookup endpoints and is intended for light personal use. Please avoid bulk scraping or frequent polling, and respect each council website's terms and availability.
Recommended Servers
playwright-mcp
A Model Context Protocol server that enables LLMs to interact with web pages through structured accessibility snapshots without requiring vision models or screenshots.
Magic Component Platform (MCP)
An AI-powered tool that generates modern UI components from natural language descriptions, integrating with popular IDEs to streamline UI development workflow.
Audiense Insights MCP Server
Enables interaction with Audiense Insights accounts via the Model Context Protocol, facilitating the extraction and analysis of marketing insights and audience data including demographics, behavior, and influencer engagement.
VeyraX MCP
Single MCP tool to connect all your favorite tools: Gmail, Calendar and 40 more.
graphlit-mcp-server
The Model Context Protocol (MCP) Server enables integration between MCP clients and the Graphlit service. Ingest anything from Slack to Gmail to podcast feeds, in addition to web crawling, into a Graphlit project - and then retrieve relevant contents from the MCP client.
Kagi MCP Server
An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
E2B
Using MCP to run code via e2b.
Neon Database
MCP server for interacting with Neon Management API and databases
Exa Search
A Model Context Protocol (MCP) server lets AI assistants like Claude use the Exa AI Search API for web searches. This setup allows AI models to get real-time web information in a safe and controlled way.
Qdrant Server
This repository is an example of how to create a MCP server for Qdrant, a vector search engine.