INDIVIDUAL MCP TOOL

get_application

One planning application in full by its Plota id (the id field from any search result): proposal, address, status, decision, dates, category, documents count, links, and on Pro the planning constraints at the site.

plota.co.uknone authenticationAvailability not checked

LIVE ENDPOINT

https://api.plota.co.uk/v1/mcp/YOUR_API_KEY

No auth detected

Connect to this endpoint to inspect the live schema for get_application and invoke it with your own arguments.

Indexed input schema

{}

Risk classification

Inferred read-only · medium confidence · heuristic, not a guarantee.

No write-capable action terms were found; this is not proof that invocation has no side effects.

Parent server

plota.co.uk

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.plota]
url = "https://api.plota.co.uk/v1/mcp/YOUR_API_KEY"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "plota": {
      "type": "http",
      "url": "https://api.plota.co.uk/v1/mcp/YOUR_API_KEY"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: plota
Remote MCP URL: https://api.plota.co.uk/v1/mcp/YOUR_API_KEY

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "plota": {
      "url": "https://api.plota.co.uk/v1/mcp/YOUR_API_KEY"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "plota": {
      "type": "http",
      "url": "https://api.plota.co.uk/v1/mcp/YOUR_API_KEY"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "plota",
  "transport": "streamable-http",
  "url": "https://api.plota.co.uk/v1/mcp/YOUR_API_KEY"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

Related tools

search_applications — The main way to find applications, and the right tool whenever any part of the question can be named as a filter.
nearby_applications — Planning applications near a point, ordered by distance: give lat and lng, a full UK postcode, or an address (geocoded live), with a radius in metres (max 5000).
application_history — The status and decision timeline of one application: every recorded status change with its date.
decision_stats — Decision times and approval rates.
search_appeals — Decided planning appeals from the Planning Inspectorate: filter by council, outcome (allowed, dismissed, split), type, decision date range, reference or postcode.
expiring_consents — Permitted full and outline consents whose statutory time limit falls in the coming months, for a council or a bounding box: sites where permission will lapse unless work starts.
associated_applications — The family an application belongs to: earlier and later applications on the same site (outline, reserved matters, amendments, discharge of conditions, appeals).
application_documents — The documents on one application's council file: title, type, date and group (decision, statements, plans, forms, comments, other), newest first.