feat: add claude-history-mcp to community extensions - #290
Conversation
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: defaults Review profile: CHILL Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughREADME.md restructures the Community Extensions project list, adds a ChangesREADME documentation
Estimated code review effort: 1 (Trivial) | ~2 minutes Possibly related PRs
Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
There was a problem hiding this comment.
Actionable comments posted: 2
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In `@README.md`:
- Line 307: Update the TODO entry in the README list to use the repository’s
established list-item marker instead of an indented en dash, and capitalize
“GitHub” in the item text.
- Line 298: Update the README install command to pin sydasif/claude-history-mcp
to a reviewed commit SHA instead of the default branch, and add a brief
trust/privacy note explaining that this MCP reads session transcripts and
command history.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
|
Neat! But that project doesn't seem to use anything from us, so I don't see how this could be categorized as a "community extension." Can you enlighten us? |
|
Looks like the project is based off the code from this library with a lot of functionality removed: https://github.com/sydasif/claude-history-mcp/blob/0d02f02472170690453ab0c3210b1012023c680f/spec.md#16-what-we-skip-vs-claude-code-log The idea is good and considered doing something similar myself, but not sure if promoting it in the top level README is quite warranted as is, since your library basically took a snapshot and won't get bug fixes and improvements. If you'd be up for redoing with this library as the parser, we could consider doing a cache refresh only mode in the CLI if that's what was stopping you? |
|
Thanks for the feedback @cboos and @daaain! You're absolutely right - the current version was a snapshot that doesn't benefit from upstream improvements. I've addressed this by creating PR #292 which adds a public library API (
The library API PR (#292) is open and passing all CodeRabbit checks. Once merged, I'll update the dependency and this PR will represent a true "community extension" that properly integrates with the ecosystem. Also noted on the "cache refresh only mode" - that would be a great addition for the CLI. Happy to contribute that once the library API is merged. Also noted on the "cache refresh only mode" - that would be a great addition for the CLI. Happy to contribute that once the library API is merged. Also noted on the "cache refresh only mode" - that would be a great addition for the CLI. Happy to contribute that once the library API is merged. Happy to adjust the README categorization once the library integration is complete! |
|
Thanks. |
Adds claude-history-mcp as a community extension in the README.
This MCP server lets Claude Code query its own session history — search messages, list sessions, retrieve transcripts, and analyze usage patterns across all your projects.
Key features:
~/.claude/projects/**/*.jsonl(session transcripts) and~/.claude/history.jsonl(command history)claude mcp add claude-history --scope user -- uvx --from git+https://github.com/sydasif/claude-history-mcp claude-history-mcpSummary by CodeRabbit
claude-history-mcp.