callsigns://districts — oeradio mcp MCP Resource

callsigns://districts is one of 6 resources on the oeradio mcp MCP server. Connect the server and your client can attach it as context.

by client

How to attach callsigns://districts from your client

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

Other resources on this server

• callsigns://license-classes
• bandplan://iaru-region1/complete
• cables://coaxial/all
• antennas://gains/all
• oeradio://tools/all

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.