Planning

What the planning MCP server does

The planning MCP server provides access to Australian planning data covering approximately 455 councils across seven states. Its listing identifies two important properties of the data: results are clause-cited, and they carry confidence tags.

Clause citations are relevant when a developer needs to trace a planning answer back to a specific provision rather than rely on an uncited summary. Confidence tags add a separate signal about the confidence associated with the returned information. Together, these fields can help an agent present planning information with more context about its source and certainty.

The stated coverage is broad but not universal: about 455 councils are included, spanning seven Australian states. The supplied material does not identify the individual councils, the states by name, or the boundaries of the dataset. Confirm coverage for a particular council before depending on the server in a production workflow.

How it works

An agent uses the planning MCP server to work with the listed Australian planning data. The available description does not specify whether access uses search, structured queries, filters, or another interaction model, so implementation details should be verified from the service documentation.

The documented output characteristics are clause citations and confidence tags. A client evaluating a result can use the citation to identify the relevant planning clause and the confidence tag to qualify how much weight to place on the result. The source material does not describe ranking, update frequency, response schemas, authentication, or how citations are formatted.

Tools and capabilities

The documented capabilities are:

• Access to Australian planning data
• Coverage of approximately 455 councils
• Coverage across seven states
• Clause-cited results
• Confidence-tagged results

These capabilities make the planning MCP server a candidate for workflows that need council planning information with source references and confidence metadata. The available material does not name individual MCP tools, parameters, return fields beyond the stated citation and confidence properties, or supported planning topics.

Limitations and notes

The council count is approximate, so it should be treated as a stated scale rather than a fixed inventory. Seven-state coverage also does not establish that every council or planning authority in those states is represented.

No README is available in the supplied material. As a result, installation steps, transport type, environment variables, client compatibility, authentication requirements, rate limits, update schedule, licensing, and detailed tool names cannot be confirmed here. The source is listed as feasibly.com.au, but the supplied description does not provide enough technical detail to infer an API contract or deployment method.

Before integrating the planning MCP server, verify that the target council is covered, inspect the citation and confidence formats, and confirm how the service is started and authenticated. These checks are especially important when an agent's output will be used for a decision that depends on a particular planning clause.