INDIVIDUAL MCP TOOL
assess_planning_approval_likelihood
Purpose: produce an evidence-weighted first-pass planning approval likelihood for a development proposal using recent nearby approvals, inferred density, proposed density and top comparable precedents.
LIVE ENDPOINT
https://mcp.atlasly.app/.well-known/oauth-protected-resource/mcp
Connect to this endpoint to inspect the live schema for assess_planning_approval_likelihood 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
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.atlasly-mcp]
url = "https://mcp.atlasly.app/.well-known/oauth-protected-resource/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"atlasly-mcp": {
"type": "http",
"url": "https://mcp.atlasly.app/.well-known/oauth-protected-resource/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: atlasly-mcp
Remote MCP URL: https://mcp.atlasly.app/.well-known/oauth-protected-resource/mcp
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": {
"atlasly-mcp": {
"url": "https://mcp.atlasly.app/.well-known/oauth-protected-resource/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"atlasly-mcp": {
"type": "http",
"url": "https://mcp.atlasly.app/.well-known/oauth-protected-resource/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "atlasly-mcp",
"transport": "streamable-http",
"url": "https://mcp.atlasly.app/.well-known/oauth-protected-resource/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
Related tools
search_tools— Discover available Atlasly tools by keyword.get_lpa_adapter_status— Purpose: inspect Atlasly top-LPA planning source adapter coverage, operational status, cache state, record counts, and geometry coverage.site_verdict— Purpose: produce the one-call Atlasly hero appraisal for a known UK site.compare_sites— Purpose: compare exactly two UK sites for the same intended use and stage using the existing Site Verdict evidence.boundary_doctor— Purpose: check a user-supplied red-line boundary before treating it as the site geometry.analyze_site— First-pass site intelligence for a UK address or postcode.check_planning_constraints— Check first-pass UK planning constraints at a site: flood zone, listed buildings, conservation areas, Article 4 Directions, Tree Preservation Orders, environmental designations (SSSI, AONB, Green Belt, ancient woodland), historic landfill, and ground conditions.check_permitted_development— Purpose: decide whether a common UK proposal is likely permitted development, prior approval, full permission, or unclear by combining GPDO Schedule 2 logic with Atlasly site constraints.