Civic Data

For agent developers

Give an agent official facts without putting an LLM in the data path.

Civic’s MCP tools call the same deterministic domain operations as the REST API. Every structured result carries source identity and freshness, while methodology and source documentation are available as MCP resources.

Connect

{
  "mcpServers": {
    "civic-data": {
      "url": "https://mcp.civicdata.co.uk/mcp"
    }
  }
}

Three useful tool patterns

  • Call resolve_location, then one atomic fire, crime, roads, planning or environment tool when you need a single sourced fact.
  • Call get_geography_profile for a ward, local authority, MSOA or London postcode district using its stable official code.
  • Call get_source_info and read the civic://methodology resource before presenting coverage or limitations.

Worked example: one ward profile

tool: get_geography_profile
arguments:
  type: ward
  identifier: E05013924
{
  "data": {
    "identifier": { "type": "ward", "code": "E05013924" },
    "crime": {
      "geographic_basis": "best_fit_lsoa",
      "latest_12_month_rate_per_1000_residents": 124.8
    }
  },
  "sources": [{ "publisher": "Metropolitan Police Service", "as_of": "2026-07" }]
}

Use the OpenAPI specification for REST contracts and llms.txt for agent-readable site discovery.

What Civic does not do

Tools do not execute arbitrary SQL, expose raw tables, create risk or desirability scores, or infer advice. Paid composed calls are an edge entitlement concern; atomic source access remains free and rate limited.