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