1. Conduid
  2. Blockchain
  3. Sessions
MCP server · Blockchain

Sessions

MCP server to search and browse Claude Code conversation history across projects

39Low

Scored 21 days ago · breakdown

About Sessions

Sessions is an MCP server in the Blockchain category: mCP server to search and browse Claude Code conversation history across projects.

The repository has 1 stars and 0 forks.

Install

From source
git clone https://github.com/nicknisi/sessions

This server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.

Tools (12)

get_activity_digestCompact digest of sessions in a date range, grouped by day and project — for weekly summaries

Parameters not published.

get_context_primerRepo-scoped primer (recent sessions in detail + older headlines) for re-injecting prior work

Parameters not published.

get_memoryApproved standing instructions and durable facts for this repo, its project groups, and cross-repo workflow rules — a bounded set of short sentences to read before starting a task. An optional `topic` narrows the result to what is relevant to the task at hand; memory approved with `--always-on` are returned regardless and come first

Parameters not published.

get_memory_recurrenceRead-only recurrence report over the memory store: VIOLATIONS (approved memories re-corrected after their `lastSeen` date), REPEATS (corrections spanning multiple sessions and dates that were never triaged), and FUZZY (middling-similarity paraphrase pairs for human confirmation). Each finding carries session links. `repo` defaults to the current repo; `all` crosses repos

Parameters not published.

get_memory_sourcesInventory every memory store the agents on this machine keep — pi-hermes-memory, Claude Code's global/per-project memory and CLAUDE.md/AGENTS.md files, Codex's rules and goals — with entry counts, durable-fact counts, and last-updated dates. Pure discovery for "what does each agent know?"

Parameters not published.

get_session_digestThe arc of one session in a single bounded call (~2k tokens): every genuine user turn paired with its exchange's final assistant reply. Long sessions elide middle exchanges, never the ends

Parameters not published.

get_session_messagesRetrieve messages from a specific session, paginated by offset and limit — pass a `messageHits[].index` from search (or a `grep_sessions` hit's `msgIndex`, or an `exchanges[].index` from the digest) as the offset. `include_tools` annotates each turn with the assistant's tool calls

Parameters not published.

get_session_metricsUsage metrics for a date range: tool/project breakdown, daily activity, active hours

Parameters not published.

grep_sessionsExhaustive literal-or-regex match over every indexed message — for "every time I said X", counts, or exact patterns where ranked search would miss some. Returns `totalHits`/`totalSessions` and hit snippets; each hit's `msgIndex` feeds `get_session_messages` directly

Parameters not published.

review_agent_memoriesRead the CONTENTS of those stores with provenance: source agent and store, scope, a durable flag (importable fact vs audit-only material), and a `similarTo` flag when an entry substantially overlaps a memory sessions already holds. Secret/injection text is withheld with a count. Filter by `agent`, narrow by `topic`; capped at 50 entries with `total`/`truncated` reporting the rest

Parameters not published.

search_sessionsRanked, top-k search across sessions by keyword; each result includes snippets, files/commands, an errored flag, a resume command, and `messageHits` — the specific matching messages (index, role, snippet). `files` and `commands` are capped at 10 and 5, with `fileCount`/`commandCount` reporting the true totals. A `files` filter answers "which sessions touched this file?" (newest first)

Parameters not published.

why_did_this_changeCorrelate a file, `path:line`, commit-ish, or free-text topic to the AI sessions behind it. Returns the resolved commit (subject, author time, files, trailers) and the sessions that produced it, each tagged `files+time` or `time-only`, with excerpts and a resume command. Read-only on git and the index — never writes to any repository

Parameters not published.

Ask AI

✦

Ask AI about Sessions

Powered by Claude · Grounded in docs

I know everything about Sessions. Ask me about installation, configuration, usage, or troubleshooting.

Security checks

6 checks have not been run yet.

Questions

About Sessions

How do I install Sessions?

No package has been published for this server, so install it from source: clone the repository and follow its README.

Is Sessions safe to use with an AI agent?

Its trust score is 39 out of 100 (low). Conduid hasn't run static security checks on this repository yet, so review the source yourself before granting it credentials. It has no ConduID identity yet, so agent calls to it are not receipted.

Is Sessions still maintained?

Conduid hasn't recorded a commit date for this repository yet. Check the repository directly for recent activity.