Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@ukpolice show me recent crimes near King's Cross"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
UK Police MCP — wraps the UK Police Data API (free, no auth)
Part of Pipeworx — an MCP gateway connecting AI agents to 1476+ live data sources.
Tool | Description |
| Get street-level crimes reported near a latitude/longitude in England, Wales or Northern Ireland, from the official police open data. Returns each crime's category, street, month and outcome status, plus the month the figures are actually for. Answers "what crime was reported near " and "how much burglary is there around these coordinates". Omit |
| List all police forces in England, Wales, and Northern Ireland. Returns force ID and name. |
| Get outcomes for crimes at a location for a given month. Returns outcome category and date for each crime. |
Related MCP server: Property Price Search MCP Server
Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
{
"mcpServers": {
"ukpolice": {
"url": "https://gateway.pipeworx.io/ukpolice/mcp"
}
}
}tools/list at https://gateway.pipeworx.io/ukpolice/mcp returns the tools in the table
above plus the shared Pipeworx meta-tools — ask_pipeworx,
discover_tools, search_within, remember/recall and the rest of the
gateway-wide set. So the tool count you see is larger than this table: a
single-pack endpoint currently lists roughly 30 shared tools alongside the
pack's own. The connection's initialize response states its exact scope, and
is the authoritative answer for a given day.
This is deliberate, not multiplexing by accident. The meta-tools are what let a
scoped connection answer a question this pack does not cover — via
ask_pipeworx, which routes across the whole catalog — without you adding a
second MCP server. There is currently no way to mount a pack endpoint without
them; if the extra schemas cost you more context than the routing is worth,
connect to the full gateway once rather than to several pack endpoints.
Or connect to the full Pipeworx gateway to get every pack's tools listed directly, instead of just this one's:
{
"mcpServers": {
"pipeworx": {
"url": "https://gateway.pipeworx.io/mcp"
}
}
}Both URLs reach the same gateway and the same 1476+ data sources. The
only difference is which pack's tools are listed directly; ask_pipeworx
reaches all of them from either one.
Instead of calling tools directly, you can ask questions in plain English — this works on the pack endpoint above as well as on the full gateway:
ask_pipeworx({ question: "your question about Ukpolice data" })The gateway picks the right tool and fills the arguments automatically.
MIT
This server cannot be deployed
Access street-level crime reports, stop and search data, and outcomes across UK police forces
Query UK Parliament, elections, crime stats, ONS census data, and national archives
Access UK air quality data, monitoring sites, and hourly pollutant measurements across regions
Search UK companies, land registry prices, charities, OS locations, and traffic data