Ai Sessions MCP Server

If you already use Ai Sessions MCP, the ai sessions mcp mcp server is the piece that lets your assistant work with it directly. An MCP server that makes sessions from Claude Code, OpenAI Codex, Gemini CLI and opencode available to any MCP compatible client.

What the server does

• Finding past solutions to similar problems
• Reviewing what you worked on recently
• Learning from previous conversations
• Resuming interrupted work

Available tools

The toolset is worth reading before you wire it up, because it tells you what the integration is really for:

• Setup — After installation, configure your MCP client to use the binary:
• Authentication — Opens your browser to generate a CLI token. The token is saved locally in ~/.aisessions/config.json
• Options — The Options tool exposed by this server
• list_available_sources — Shows which AI CLI coding agents have sessions on your system
• list_sessions — The list_sessions tool exposed by this server
• search_sessions — Searches session content using BM25 ranking. Returns results sorted by relevance score with contextual snippets
• get_session — The get_session tool exposed by this server

Installation

Setup follows the usual MCP pattern — install or clone the server, register it in your client's configuration file, restart the client.

Where it fits

Plenty of browser automation servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Ai Sessions MCP's toolset — Setup, Authentication, Options and 4 more — is a fair guide to whether it matches your workflow. It is maintained by yoavf; worth a glance at recent repository activity before you build anything load-bearing on it.

We check each listing at SyncDev against the project's documentation before it goes live — if something here drifts out of date, it is a bug worth reporting.

Worth knowing first

• It runs with your machine's permissions. That is convenient and also the reason to think about what you point it at before you approve a tool call.
• Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.