list_available_sourcesLABSCO SUMMARY
Yesterday's session, searchable — including the ones from a different agent.
The transcripts were already sitting in ~/.claude, ~/.codex and their equivalents; what was missing is any way to ask them a question. search_sessions ranks by relevance and returns the excerpt, so "how did I fix that auth bug" resolves without you remembering which agent you were using at the time, and get_session pages the actual conversation into the one you are in now.
What it is
A Go binary that reads the session transcripts those CLI coding agents already write to disk and serves them over MCP. It reads the local stores through source-specific adapters; it does not launch the agent CLIs.
What you get
- Recent sessions across all projects, newest first, filtered by source or by project directory
- Keyword search over session content, ranked with BM25, each hit carrying a contextual snippet
- Any session's full transcript, paged so a long one does not arrive in one piece
- Which source adapters the running server can actually see on this machine
- One place for Claude Code, Gemini CLI, OpenAI Codex, opencode, Mistral Vibe and GitHub Copilot CLI history
Requirements
A single binary. The install script at https://aisessions.dev/install.sh puts it in ~/.aisessions/bin, or take a release build for macOS, Linux or Windows amd64; INSTALL_DIR moves it elsewhere. Building from source needs Go 1.25.13 or later. Point your client at the binary path over stdio. Nothing to authorize for reading — the session files are already on the machine. The separate aisessions login and aisessions upload commands exist for publishing a transcript to aisessions.dev and are not part of the server.
Setup effort
One command — curl -fsSL https://aisessions.dev/install.sh | bash
USE CASES
01
Continuing a session you started in another agent
List recent sessions filtered to that source, then page its transcript into the client you are in now.
02
Finding how you solved this the last time
Search every stored session by keyword and get ranked hits with the matching excerpt, not just file names.
03
Reviewing what you worked on this week
List recent sessions for one project directory, newest first.
04
Checking which agents this machine has history for
Ask which source adapters the running server can see before you search across them.
4 tools
Listed in project docs. Your client may show a different list.
list_sessionssearch_sessionsget_sessionBEFORE YOU INSTALL
What to know first
Tools you get
4 tools named in the project's documentation.
Where it runs
All 3 documented clients run the server on your machine.
INSTALLATION
Connect your client
Server setup
TERMINAL
curl -fsSL https://aisessions.dev/install.sh | bashMCP Clients
Claude Code
CLAUDE CODE · TERMINAL
claude mcp add --scope user --transport stdio ai-sessions -- ~/.aisessions/bin/aisessionsCodex
CODEX · TOML
[mcp_servers.ai_sessions]
command = "/Users/<YOUR_USERNAME>/.aisessions/bin/aisessions"Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"ai-sessions": {
"command": "/Users/<YOUR_USERNAME>/.aisessions/bin/aisessions"
}
}
}
