local_intel_tide — local intel MCP Tool
local_intel_tide
(local intel tide) is one of 27 tools on the
local intel
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call local_intel_tide from your client
- Claude Code local intel local_intel_tide run in your project directory
- Claude Desktop local intel local_intel_tide ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor local intel local_intel_tide ~/.cursor/mcp.json
- VS Code local intel local_intel_tide .vscode/mcp.json
- Zed local intel local_intel_tide ~/.config/zed/settings.json
- Windsurf local intel local_intel_tide ~/.codeium/windsurf/mcp_config.json
- Cline local intel local_intel_tide ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI local intel local_intel_tide ~/.gemini/settings.json
- Grok local intel local_intel_tide .mcp.json (in your project root)
- ChatGPT local intel local_intel_tide Settings → Connectors → Advanced → Developer mode
- Claude.ai local intel local_intel_tide Settings → Connectors → Add custom connector
- LangChain local intel local_intel_tide pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http local-intel https://gsb-swarm-production.up.railway.app/api/local-intel/mcpOther tools on this server
- local_intel_query
- local_intel_context
- local_intel_search
- local_intel_nearby
- local_intel_zone
- local_intel_corridor
- local_intel_changes
- local_intel_stats
- local_intel_signal
- local_intel_bedrock
- local_intel_for_agent
- local_intel_oracle
- local_intel_sector_gap
- local_intel_realtor
- local_intel_healthcare
- local_intel_retail
- local_intel_construction
- local_intel_restaurant
- local_intel_ask
- local_intel_compare
- local_intel_project
- local_intel_rfq
- local_intel_rfq_status
- local_intel_book
- local_intel_decline_response
- local_intel_complete
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 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.