wanderloop.research_place — Atlasemoji MCP Tool
wanderloop.research_place
(wanderloop research place) is one of 17 tools on the
Atlasemoji
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call wanderloop.research_place from your client
- Claude Code Atlasemoji wanderloop.research_place run in your project directory
- Claude Desktop Atlasemoji wanderloop.research_place ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Atlasemoji wanderloop.research_place ~/.cursor/mcp.json
- VS Code Atlasemoji wanderloop.research_place .vscode/mcp.json
- Zed Atlasemoji wanderloop.research_place ~/.config/zed/settings.json
- Windsurf Atlasemoji wanderloop.research_place ~/.codeium/windsurf/mcp_config.json
- Cline Atlasemoji wanderloop.research_place ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Atlasemoji wanderloop.research_place ~/.gemini/settings.json
- Grok Atlasemoji wanderloop.research_place .mcp.json (in your project root)
- ChatGPT Atlasemoji wanderloop.research_place Settings → Connectors → Advanced → Developer mode
- Claude.ai Atlasemoji wanderloop.research_place Settings → Connectors → Add custom connector
- LangChain Atlasemoji wanderloop.research_place pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http mcp https://atlasemoji.com/api/mcpOther tools on this server
- list_capabilities
- get_datasynch_run_status
- get_failed_runs
- validate_manifest_schema
- get_manifest_summary
- validate_coordinates
- validate_geojson
- detect_location_columns
- preview_geofence
- check_point_in_geofence
- detect_file_schema
- preview_datasynch_rows
- suggest_field_mapping
- summarize_workspace_activity
- wanderloop.get_manifest
- wanderloop.list_provider_capabilities
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.