session_end — Snapback MCP Tool
session_end
(session end) is one of 23 tools on the
Snapback
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call session_end from your client
- Claude Code Snapback session_end run in your project directory
- Claude Desktop Snapback session_end ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Snapback session_end ~/.cursor/mcp.json
- VS Code Snapback session_end .vscode/mcp.json
- Zed Snapback session_end ~/.config/zed/settings.json
- Windsurf Snapback session_end ~/.codeium/windsurf/mcp_config.json
- Cline Snapback session_end ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Snapback session_end ~/.gemini/settings.json
- Grok Snapback session_end .mcp.json (in your project root)
- ChatGPT Snapback session_end Settings → Connectors → Advanced → Developer mode
- Claude.ai Snapback session_end Settings → Connectors → Add custom connector
- LangChain Snapback session_end pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http snapback https://api.snapback.sh/mcpOther tools on this server
- diagnose_trace
- diagnose_batch
- get_verdict
- preflight
- submit_feedback
- get_request_status
- my_usage
- my_impact
- what_others_did
- report_outcome
- recommend_failover
- cascade_root
- suggest_budget_recovery
- request_pattern
- detect_loop
- session_start
- session_step
- agent_memory
- budget_guard
- convert_trace
- search_docs
- diagnose_infra_error
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.