property_area — L50 Data Tools MCP Tool
property_area
(property area) is one of 24 tools on the
L50 Data Tools
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call property_area from your client
- Claude Code L50 Data Tools property_area run in your project directory
- Claude Desktop L50 Data Tools property_area ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor L50 Data Tools property_area ~/.cursor/mcp.json
- VS Code L50 Data Tools property_area .vscode/mcp.json
- Zed L50 Data Tools property_area ~/.config/zed/settings.json
- Windsurf L50 Data Tools property_area ~/.codeium/windsurf/mcp_config.json
- Cline L50 Data Tools property_area ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI L50 Data Tools property_area ~/.gemini/settings.json
- Grok L50 Data Tools property_area .mcp.json (in your project root)
- ChatGPT L50 Data Tools property_area Settings → Connectors → Advanced → Developer mode
- Claude.ai L50 Data Tools property_area Settings → Connectors → Add custom connector
- LangChain L50 Data Tools property_area pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http l50-uk-data https://api.l50automation.com/mcpOther tools on this server
- epc_areas
- ebay_market
- companies_new
- companies_overdue
- companies_changes
- companies_changes_feed
- tenders
- youtube_transcript
- vinted_search
- shopify_store
- poshmark_search
- reverb_search
- mot_history
- compare_resale
- companies_profile
- companies_search
- companies_officer
- property_rents
- property_flood
- property_compare
- tenders_supplier
- tenders_buyer
- companies_changes_feed_sample
This list was read from the server itself, by connecting to it and calling tools/list on 11 November 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.