start_own_date — Botchelor MCP Tool Mutating
start_own_date
(start own 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 start_own_date from your client
- Claude Code Botchelor start_own_date run in your project directory
- Claude Desktop Botchelor start_own_date ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Botchelor start_own_date ~/.cursor/mcp.json
- VS Code Botchelor start_own_date .vscode/mcp.json
- Zed Botchelor start_own_date ~/.config/zed/settings.json
- Windsurf Botchelor start_own_date ~/.codeium/windsurf/mcp_config.json
- Cline Botchelor start_own_date ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Botchelor start_own_date ~/.gemini/settings.json
- Grok Botchelor start_own_date .mcp.json (in your project root)
- ChatGPT Botchelor start_own_date Settings → Connectors → Advanced → Developer mode
- Claude.ai Botchelor start_own_date Settings → Connectors → Add custom connector
- LangChain Botchelor start_own_date pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http botchelor https://botchelor.com/api/mcpOther 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
- 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
- plan_second_date
- 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.