Boundr - UK Boundary Data

Claude Desktop

Paste this block into your claude_desktop_config.json (~/Library/Application Support/Claude/claude_desktop_config.json on macOS, %APPDATA%\Claude\claude_desktop_config.json on Windows), then restart Claude Desktop.

{
  "mcpServers": {
    "boundr": {
      "url": "https://mcp.boundr.dev/sse"
    }
  }
}

Claude Code

Run this command once to register Boundr in your user-level Claude Code config:

claude mcp add --transport sse boundr https://mcp.boundr.dev/sse

Claude.ai

In Claude.ai go to Settings > Connectors > Add custom connector and paste the URL below. Requires Pro or above.

https://mcp.boundr.dev/sse

Connect Boundr to ChatGPT via Connectors. In ChatGPT, go to Settings > Connectors > Create and paste the URL below.

https://mcp.boundr.dev/sse

Connectors are available on ChatGPT Plus, Team, and Enterprise. Once connected, Boundr tools are available when you click the + button in the chat composer and select Boundr from the list.

Add Boundr to OpenCode by adding a mcp entry to your opencode.json config file:

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "boundr": {
      "type": "remote",
      "url": "https://mcp.boundr.dev/sse"
    }
  }
}

Merge this into your existing opencode.json if you already have one. OpenCode will discover and invoke the Boundr tools automatically when you ask about UK administrative boundaries.

Copy this plain-text prompt into any LLM chat (Claude web, ChatGPT, etc.) to describe the Boundr tools and how to use them.

I have access to a Model Context Protocol (MCP) server called "boundr" at https://mcp.boundr.dev/sse.

It provides UK administrative boundary data through the following tools:

- list_boundary_type_codes() — Returns a mapping of boundary type codes to human-readable labels (for example, LBO = London Borough, CTY = County). Use this first when you need to filter by boundary type.
- search_boundaries_by_name(name, boundary_type=None) — Case-insensitive partial name search. Returns lightweight metadata only, not geometry.
- find_boundaries_at_point(lat, lng, boundary_types=None) — Returns all boundaries that contain the given lat/lng point.
- get_boundary_by_code(code) — Looks up metadata by ONS LAU / GSS code (for example, E09000012).
- get_boundary_geojson_by_code(code) — Returns the full GeoJSON Feature for a boundary. This is the most expensive call because it includes geometry; only use it when I explicitly ask for a map, shape, or boundary outline.

When I ask questions about UK administrative boundaries, choose the cheapest tool that answers the question. Prefer metadata-only tools over geometry unless I specifically ask for a visualisation or boundary shape.