loc_id Guide — DaedalMap Tornado Events MCP Resource

loc_id Guide is one of 6 resources on the DaedalMap Tornado Events MCP server. Connect the server and your client can attach it as context.

by client

How to attach loc_id Guide from your client

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

Other resources on this server

• Guide
• Catalog
• Access Model
• Tornadoes Pack
• Public Links

DaedalMap Tornado Events also offers 1 prompt — things you invoke, where a resource is context you attach.

Read from the server itself, by connecting to it and calling resources/list on 24 September 2026. A listing does not declare its resources, so asking is the only way to know them, and this is what the server actually offers rather than what its listing claims. Names only are stored; connect the server for each resource's type and contents.