find_areas — Close Knit MCP Tool Read-only

find_areas (find areas) is one of 18 tools on the Close Knit MCP server. Connect the server and your client discovers it on the handshake.

by client

How to call find_areas from your client

Claude Code Close Knit find_areas run in your project directory
Claude Desktop Close Knit find_areas ~/Library/Application Support/Claude/claude_desktop_config.json
Cursor Close Knit find_areas ~/.cursor/mcp.json
VS Code Close Knit find_areas .vscode/mcp.json
Zed Close Knit find_areas ~/.config/zed/settings.json
Windsurf Close Knit find_areas ~/.codeium/windsurf/mcp_config.json
Cline Close Knit find_areas ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
Gemini CLI Close Knit find_areas ~/.gemini/settings.json
Grok Close Knit find_areas .mcp.json (in your project root)
ChatGPT Close Knit find_areas Settings → Connectors → Advanced → Developer mode
Claude.ai Close Knit find_areas Settings → Connectors → Add custom connector
LangChain Close Knit find_areas pip install langchain-mcp-adapters

Fastest route

claude mcp add --transport http close-knit https://getcloseknit.com/mcp

Other tools on this server

open_shared_search
find_similar_areas
assess_listing
describe_data
get
query
get_places
search
fetch
match_areas
search_places
get_commute
get_listing_search_links
build_watch_spec
check_area_rent
send_feedback
rate_answer

This list was read from the server itself, by connecting to it and calling tools/list on 14 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.

Close Knit MCP server