Borrowing it
Nothing to install: this file belongs to vltansky/cursor-chat-history-mcp. Take a copy, put it at the same path in your own repository, and replace the rules that are about this project with yours.
curl -O https://raw.githubusercontent.com/vltansky/cursor-chat-history-mcp/main/AGENTS.mdgit clone --depth 1 https://github.com/vltansky/cursor-chat-history-mcpWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/instructions/vltansky/cursor-chat-history-mcp/agents-md)<a href="https://agentmods.dev/instructions/vltansky/cursor-chat-history-mcp/agents-md"><img src="https://agentmods.dev/badge/instructions/vltansky/cursor-chat-history-mcp/agents-md.svg" alt="Measured on agentmods" height="20"></a>What it costs to keep this loaded
Counted locally with the o200k_base tokenizer, which is exact for GPT models; Claude uses its own tokenizer and its counts differ. Treat this as one consistent yardstick across the catalogue rather than a bill. Prices are per million input tokens.
| Model | Per session | Once invoked |
|---|---|---|
| Fable 5.1 | $0.02766 | $0.02766 |
| Opus 5 | $0.01383 | $0.01383 |
| Sonnet 5 | $0.00553 | $0.00553 |
| Haiku 4.5 | $0.00277 | $0.00277 |
Grade A, and why
cursor-chat-history-mcp AGENTS.md scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 8d ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
How it starts
The opening of the file, as written. The whole thing — 404 lines — stays where its author put it; the contents beside it link to each section on GitHub.
Cursor Conversations MCP Server - Project Overview
Core Concept
This project creates an MCP (Model Context Protocol) server that exposes your Cursor conversation history to AI assistants like Claude. It acts as a bridge between your local Cursor chat database and AI tools.
Primary Goal
Enable AI assistants to analyze your actual coding conversations to provide personalized, context-aware assistance based on your real development patterns and history.
Key Value Proposition
- Personalized Coding Rules: Generate coding standards from your actual conversations, not generic best practices
- Pattern Recognition: Identify recurring themes and solutions in your development work
- Context-Aware Help: Get assistance informed by your specific projects and coding style
- Historical Insights: Learn from past problem-solving sessions and apply proven solutions
How It Works
- Local Access: Reads your Cursor conversation database directly (no external services)
- MCP Protocol: Exposes conversation data through standardized MCP tools
- AI Integration: AI assistants can query, analyze, and extract insights from your chat history
- Privacy First: All data stays local - no external API calls or data sharing
Common Use Cases
"Analyze my React conversations and create component guidelines""Generate TypeScript rules based on my actual coding patterns""Find similar debugging sessions and extract solutions""Create project documentation from relevant conversations"
Technical Architecture
- Database: SQLite access to Cursor's conversation storage at
src/database/ - MCP Server: TypeScript implementation at
src/server.ts - Tools: Conversation analysis tools at
src/tools/ - Entry Point: Main configuration in
package.jsonandREADME.md
General Project Guidelines
Use npm for package management
Code Organization
- Follow the established directory structure in
src/ - Group related functionality in modules
- Use barrel exports for clean public APIs
What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 8d ago First seen · 404 lines · 2,766 tokens per session scan A 9b27915771ca
cursor-chat-history-mcp AGENTS.md is an instructions file published in the GitHub repository vltansky/cursor-chat-history-mcp (33 stars, last pushed 7mo ago), licensed MIT. It adds 2,766 tokens to every session, about $0.0138 per session on Opus 5. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other instructions, from other repositories
next.js AGENTS.md
AGENTS.md instructions for vercel/next.js, covering next.js development guide, codebase structure, monorepo overview, core package: packages/next and other important packages.
codex AGENTS.md
AGENTS.md instructions for openai/codex, covering rust/codex-rs, the codex-core crate, code review rules, crate api surface and model visible context.
vscode buildNext.instructions.md
Working notes and architecture documentation for the new esbuild-based build system in build/next. Use when making changes to the new build pipeline (transpile/bundle commands, NLS plugin, source-map handling, resource copying, or self-hosting watch tasks).
vscode oss-third-party-notices.instructions.md
Instructions for microsoft/vscode, covering vs code oss third-party-notices pipeline, architecture, pipeline flow in ci, applying the notice (cutover) and fallback chain (never fail the build).
langchain AGENTS.md
AGENTS.md instructions for langchain-ai/langchain, covering global development guidelines for the langchain monorepo, corridor security analysis, project architecture and context, monorepo structure and development tools & commands.
spec-kit AGENTS.md
AGENTS.md instructions for github/spec-kit, covering agents.md, about spec kit and specify, quickstart — add a new integration in 5 steps, integration architecture and integrationmanifest — file tracking.