get_places — Close Knit MCP Tool Read-only

get_places (get places) 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 get_places from your client

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

Fastest route

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

Other tools on this server

find_areas
open_shared_search
find_similar_areas
assess_listing
describe_data
get
query
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