Cursor Chat HistorySAFE
Overview
From the repository's own README, as read at the audited commit. Badges and raw HTML are left out.
Connect your Cursor conversations to your git history.
Why?
You make a commit. Weeks later you wonder: "Why did I write it this way?"
The git message says fix auth bug but the real context - the debugging session, the alternatives considered, the AI suggestions - lives in a Cursor conversation you'll never find again.
This MCP server automatically links your Cursor conversations to git commits. When you revisit code, the AI assistant can pull up the original discussion.
Quick Start
Add to .cursor/mcp.json:
{
"mcpServers": {
"cursor-chat-history": {
"command": "npx",
"args": ["-y", "--package=cursor-chat-history-mcp", "cursor-chat-history-mcp"]
}
}
}That's it. Hooks install automatically on first use.
What You Can Do
Find Context for Code
"What was the context behind commit abc123?" "Find the conversation that led to this fix" "Show discussions about auth.ts from the last month"
Search Your Chat History
"Find all debugging sessions about performance" "Search conversations mentioning useState" "List recent conversations in this project"
Extract Patterns
"Create TypeScript guidelines from my actual usage" "Extract error handling patterns from my conversations" "Summarize my React patterns from chat history"
Available Tools
Git Linker
Chat History
d521b8b0bab0OBSERVED · 2026-10-08Connect
Built from this server's own package name, version and transport as found in its source — not copied from anyone's documentation, so it cannot drift against a page we do not control.
claude mcp add cursor-chat-history-mcp -- npx -y [email protected]
{
"mcpServers": {
"cursor-chat-history-mcp": {
"command": "npx",
"args": [
"-y",
"[email protected]"
]
}
}
}Exposed tools (8)
6 read · 2 write · 0 destructive.
| Tool | Risk | Description |
|---|---|---|
get_commit_conversations | write | Get Cursor conversations linked to a specific git commit. Returns commit metadata plus linked conversations with confidence scores. Use this to find the discussion context for a commit. |
get_conversation | read | |
get_conversation_analytics | read | |
get_file_context | read | |
link_conversation_commit | write | Manually link a Cursor conversation to a git commit. Creates a manual link with specified confidence. Use this when the automatic linking missed a connection, or to explicitly associate a conversation with a commit. |
list_conversation_commits | read | List git commits linked to Cursor conversations. Filter by conversation ID, project path, or file path. Returns conversation metadata plus linked commits with confidence scores and matched files. Use this to understand the git history associated with your conversations. |
list_conversations | read | |
search_conversations | read |
Trust audit
SAFEgrade B · trust 89/100 Nothing in the source contradicts what it says it does. Grade A is reserved for packages that have also passed the behavioural sandbox.
| Layer | What it checks | Result |
|---|---|---|
| L0 | Provenance & inventory | WARN |
| L1 | Static analysis of the code | PASS |
| L2 | Instruction surface (what it tells the agent) | PASS |
| L3 | Class-specific surface | PASS |
| L4 | Behavioural (sandbox) | SKIPPED |
What the source does
- Filesystem
- declared (5 observation(s))
- Network
- none-observed
- Shell
- declared (1 observation(s))
- Dependencies
- not all pinned
- Secrets in source
- none-found
Findings (7)
install-state.gz
import { LinksDatabase } from '../../links-database.js';import { ClaudeCodeReader } from '../../../database/claude-code-reader.js';import type { LinkCommandResult } from '../../types.js';import { LinksDatabase } from '../../links-database.js';import { CursorDatabaseReader } from '../../../database/reader.js';@modelcontextprotocol/sdk, better-sqlite3, zod, @types/better-sqlite3, @types/node, @vitest/ui, nodemon, shx
Gates applied: no_behavioural_pass.
d521b8b0bab0full audit observations/trust-audit/mcp-server/vltansky__cursor-chat-history-1.json · Report an issue / request a re-scanAudit history
Every audit this server has had. A grade with a past is a grade somebody is still checking.
| Date | Source | Verdict | Grade | Score | Change |
|---|---|---|---|---|---|
| 2026-10-08 | d521b8b0bab0 | SAFE | B | 89 | first audit |
Questions
What tools does Cursor Chat History expose?
8 in total: 6 read-only, 2 that write, and 0 that can delete or overwrite. Every one is listed on this page with its risk.
Is Cursor Chat History safe to connect to an agent?
The audit found nothing in the source that contradicts what it says it does, and graded it B (89/100). Grade A is held back for packages that have also passed a sandboxed behavioural run, which is why a clean server reads B.
What credentials does Cursor Chat History need?
No credential environment variables were found in its source, so it appears to need none.
How does Cursor Chat History run?
It speaks stdio, so it runs as a local process your client starts. It is published on npm as cursor-chat-history-mcp at 0.2.1.
How current is this page?
The grade is for one exact copy of the source (d521b8b0bab0), read on 2026-10-08. The repository is watched and re-audited when it changes.