radio-schedule — cwi discovery engine MCP Resource
radio-schedule
is one of 3 resources on the
cwi discovery engine
MCP server. Connect the server and your client can attach it as context.
by client
How to attach radio-schedule from your client
- Claude Code cwi discovery engine Resource/radio-schedule run in your project directory
- Claude Desktop cwi discovery engine Resource/radio-schedule ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor cwi discovery engine Resource/radio-schedule ~/.cursor/mcp.json
- VS Code cwi discovery engine Resource/radio-schedule .vscode/mcp.json
- Zed cwi discovery engine Resource/radio-schedule ~/.config/zed/settings.json
- Windsurf cwi discovery engine Resource/radio-schedule ~/.codeium/windsurf/mcp_config.json
- Cline cwi discovery engine Resource/radio-schedule ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI cwi discovery engine Resource/radio-schedule ~/.gemini/settings.json
- Grok cwi discovery engine Resource/radio-schedule .mcp.json (in your project root)
- ChatGPT cwi discovery engine Resource/radio-schedule Settings → Connectors → Advanced → Developer mode
- Claude.ai cwi discovery engine Resource/radio-schedule Settings → Connectors → Add custom connector
- LangChain cwi discovery engine Resource/radio-schedule pip install langchain-mcp-adapters
Other resources on this server
cwi discovery engine also offers 5 prompts — things you invoke, where a resource is context you attach.
Read from the server itself, by connecting to it and calling resources/list on 14 November 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.