getting_started — Homerun MCP by usefulapi MCP Prompt
getting_started
is one of 6 prompts on the
Homerun MCP by usefulapi
MCP server. Connect the server and it appears in your client, ready to invoke.
by client
How to invoke getting_started from your client
- Claude Code Homerun MCP by usefulapi Prompt/getting_started run in your project directory
- Claude Desktop Homerun MCP by usefulapi Prompt/getting_started ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Homerun MCP by usefulapi Prompt/getting_started ~/.cursor/mcp.json
- VS Code Homerun MCP by usefulapi Prompt/getting_started .vscode/mcp.json
- Zed Homerun MCP by usefulapi Prompt/getting_started ~/.config/zed/settings.json
- Windsurf Homerun MCP by usefulapi Prompt/getting_started ~/.codeium/windsurf/mcp_config.json
- Cline Homerun MCP by usefulapi Prompt/getting_started ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Homerun MCP by usefulapi Prompt/getting_started ~/.gemini/settings.json
- Grok Homerun MCP by usefulapi Prompt/getting_started .mcp.json (in your project root)
- ChatGPT Homerun MCP by usefulapi Prompt/getting_started Settings → Connectors → Advanced → Developer mode
- Claude.ai Homerun MCP by usefulapi Prompt/getting_started Settings → Connectors → Add custom connector
- LangChain Homerun MCP by usefulapi Prompt/getting_started pip install langchain-mcp-adapters
Other prompts on this server
Read from the server itself, by connecting to it and calling prompts/list on 14 November 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.