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