node804-claude-code-mcp
Related Servers
Alternatives to node804-claude-code-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceAn MCP server that enables users to retrieve, filter, and search through Claude Code conversation history stored in local projects. It provides tools for listing projects and sessions, paginating through message history, and searching across conversations with keyword filtering.421 npm11MIT
- FlicenseAqualityDmaintenanceFork-aware MCP server for searching and navigating Claude Code session history.6-
- AlicenseBqualityDmaintenanceMCP server for managing Claude Code conversation sessions12MIT
- AlicenseNot gradedqualityCmaintenanceA read-only MCP server that enables Cursor or Qoder to query locally stored past agent conversations, per-file AI edit history, and recent sessions through keyword search and history tools.1MIT
- AlicenseAqualityAmaintenanceLocal, read-only MCP server of Caprock: lets a coding agent recall earlier Claude Code and Codex sessions on the same machine (memories, decisions, session summaries, cost and CI status). Nothing leaves the laptop.1250Apache 2.0
- AlicenseBqualityDmaintenanceMCP server for accessing Claude Code plugins. Enables retrieving plugin lists and detailed information via MCP clients like Claude Desktop, Cursor.2MIT
TDQS
Scored across 6 tools
Each tool targets a unique aspect: server_status for config, list_claude_projects for projects, list_claude_sessions for sessions, search_claude_sessions for full-text search, get_claude_session for transcripts, and get_claude_session_stats for metrics. There is no functional overlap.
Most tools follow a verb_noun pattern (list_claude_projects, list_claude_sessions, search_claude_sessions, get_claude_session, get_claude_session_stats). server_status is a slight deviation (noun_noun) but still clear and readable.
6 tools is well-scoped for a Claude Code session server. It covers listing, searching, retrieving details, and stats without being bloated or insufficient.
The tool surface covers core read operations for projects and sessions, including search and statistics. No obvious missing functionality for inspection, though write/delete operations are absent by design (sessions are managed externally).