research_location — 2b2t Atlas MCP Tool
research_location
(research location) is one of 25 tools on the
2b2t Atlas
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call research_location from your client
- Claude Code 2b2t Atlas research_location run in your project directory
- Claude Desktop 2b2t Atlas research_location ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor 2b2t Atlas research_location ~/.cursor/mcp.json
- VS Code 2b2t Atlas research_location .vscode/mcp.json
- Zed 2b2t Atlas research_location ~/.config/zed/settings.json
- Windsurf 2b2t Atlas research_location ~/.codeium/windsurf/mcp_config.json
- Cline 2b2t Atlas research_location ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI 2b2t Atlas research_location ~/.gemini/settings.json
- Grok 2b2t Atlas research_location .mcp.json (in your project root)
- ChatGPT 2b2t Atlas research_location Settings → Connectors → Advanced → Developer mode
- Claude.ai 2b2t Atlas research_location Settings → Connectors → Add custom connector
- LangChain 2b2t Atlas research_location pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http 2b2t-atlas https://api.blackportal.cloud/mcpOther tools on this server
- get_location
- get_warps
- find_nocom_portals
- search_nocom_signs
- research_nocom_area
- get_render_metadata
- find_nocom_storage
- get_highway
- get_world_downloads
- research_area
- find_recently_added_or_modified
- find_locations_by_time_range
- get_nocom_dataset
- get_nocom_periods
- search_locations
- find_highways_near_location
- search_groups
- search_highways
- get_nocom_highway_activity
- find_locations_near
- find_preserved_builds
- get_group
- get_group_builds
- get_dataset_stats
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.