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