fly_a_course — livedot MCP MCP Prompt
fly_a_course
is one of 3 prompts on the
livedot MCP
MCP server. Connect the server and it appears in your client, ready to invoke.
by client
How to invoke fly_a_course from your client
- Claude Code livedot MCP Prompt/fly_a_course run in your project directory
- Claude Desktop livedot MCP Prompt/fly_a_course ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor livedot MCP Prompt/fly_a_course ~/.cursor/mcp.json
- VS Code livedot MCP Prompt/fly_a_course .vscode/mcp.json
- Zed livedot MCP Prompt/fly_a_course ~/.config/zed/settings.json
- Windsurf livedot MCP Prompt/fly_a_course ~/.codeium/windsurf/mcp_config.json
- Cline livedot MCP Prompt/fly_a_course ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI livedot MCP Prompt/fly_a_course ~/.gemini/settings.json
- Grok livedot MCP Prompt/fly_a_course .mcp.json (in your project root)
- ChatGPT livedot MCP Prompt/fly_a_course Settings → Connectors → Advanced → Developer mode
- Claude.ai livedot MCP Prompt/fly_a_course Settings → Connectors → Add custom connector
- LangChain livedot MCP Prompt/fly_a_course pip install langchain-mcp-adapters
Other prompts on this server
livedot MCP also offers 2 resources — data you attach as context, where a prompt is something you run.
Read from the server itself, by connecting to it and calling prompts/list on 18 October 2026.
A listing does not declare its prompts, 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 prompt's arguments.