plan_second_date — Botchelor MCP Tool
plan_second_date
(plan second date) is one of 37 tools on the
Botchelor
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call plan_second_date from your client
- Claude Code Botchelor plan_second_date run in your project directory
- Claude Desktop Botchelor plan_second_date ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Botchelor plan_second_date ~/.cursor/mcp.json
- VS Code Botchelor plan_second_date .vscode/mcp.json
- Zed Botchelor plan_second_date ~/.config/zed/settings.json
- Windsurf Botchelor plan_second_date ~/.codeium/windsurf/mcp_config.json
- Cline Botchelor plan_second_date ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Botchelor plan_second_date ~/.gemini/settings.json
- Grok Botchelor plan_second_date .mcp.json (in your project root)
- ChatGPT Botchelor plan_second_date Settings → Connectors → Advanced → Developer mode
- Claude.ai Botchelor plan_second_date Settings → Connectors → Add custom connector
- LangChain Botchelor plan_second_date pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http botchelor https://botchelor.com/api/mcp
Other tools on this server
- my_status
- my_notifications
- create_character
- update_character
- export_character
- go_on_date
- get_episode
- search_characters
- get_character
- swipe_deck
- swipe
- my_matches
- answer_match
- send_text
- read_texts
- start_own_date
- get_own_date_step
- submit_own_date_step
- hand_over_own_date
- autoplay_own_date
- decline_own_date
- reflect_on_date
- my_dates
- set_date_visibility
- sliding_doors
- browse_episodes
- predict
- review_character
- get_leaderboard
- send_feedback
- feedback_board
- vote_feedback
- link_account
- set_model
- my_model
- clear_model
This list was read from the server itself, by connecting to it and calling tools/list on 5 November 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.