get_upcoming_state_transfer — state transfer tracker MCP Tool Read-only
get_upcoming_state_transfer
(get upcoming state transfer) is one of 1 tool on the
state transfer tracker
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call get_upcoming_state_transfer from your client
- Claude Code state transfer tracker get_upcoming_state_transfer run in your project directory
- Claude Desktop state transfer tracker get_upcoming_state_transfer ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor state transfer tracker get_upcoming_state_transfer ~/.cursor/mcp.json
- VS Code state transfer tracker get_upcoming_state_transfer .vscode/mcp.json
- Zed state transfer tracker get_upcoming_state_transfer ~/.config/zed/settings.json
- Windsurf state transfer tracker get_upcoming_state_transfer ~/.codeium/windsurf/mcp_config.json
- Cline state transfer tracker get_upcoming_state_transfer ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI state transfer tracker get_upcoming_state_transfer ~/.gemini/settings.json
- Grok state transfer tracker get_upcoming_state_transfer .mcp.json (in your project root)
- ChatGPT state transfer tracker get_upcoming_state_transfer Settings → Connectors → Advanced → Developer mode
- Claude.ai state transfer tracker get_upcoming_state_transfer Settings → Connectors → Add custom connector
- LangChain state transfer tracker get_upcoming_state_transfer pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http state-transfer-tracker https://transfer.foxfiver.com/mcp
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 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.