pulsemcp verified Safe content atomic mcp-remote

Cursor Chat History

This MCP server provides AI assistants access to Cursor chat history for analysis and insights, enabling personalized coding assistance based on actual development patterns. Built using TypeScript with better-sqlite3 and the MCP SDK, it reads local Cursor conversation databases directly without external services, supporting both legacy and modern conversation formats with tools for listing, searching, and retrieving full conversations, plus advanced analytics including usage patterns, file activity, programming language distribution, and relationship detection between conversations. The implementation uses a summary-first approach for context efficiency, allowing users to browse conversation summaries before diving into full content, and includes data extraction capabilities with JSON, CSV, and graph export formats, making it valuable for generating personalized coding rules from actual usage patterns, extracting best practices from past problem-solving sessions, and creating project documentation based on real development conversations.

Cognium trust score

85%

Tier

Verified

Composite of vulnerability cleanliness, spec conformance, provenance, stability, and usage signals — scanned and weighted by Cognium. Human and agent signals are tracked separately. Last scanned 2026-09-19.

Scan details: Circle-IR · 2026-09-19 · Appeal

View full trust & usage report →

Metadata

Version: 1.0.0
Skill type: atomic
Execution layer: mcp-remote
Category: database
Source: PulseMCP
Repository: github.com/vltansky/cursor-chat-history-mcp
Author type: human
Last scanned: 2026-09-19
Updated: 2026-09-19

View source Find related skills

MCP

Resolve Cursor Chat History from your agent

Streamable HTTP transport at https://api.skillsregistry.net/mcp. No auth for read tools. Discovery: .well-known/mcp.json.

One command in your shell — Claude Code wires it up and verifies the connection. Run /mcp in any session to confirm.

claude mcp add --transport http --scope user skillsregistry https://api.skillsregistry.net/mcp

Swap --scope user for --scope project to commit it to .mcp.json.

Your client Same endpoint everywhere; only the config key differs. The full list is in the descriptor.

Claude Desktop · Settings → Connectors → Add custom connector

https://api.skillsregistry.net/mcp

Paste the URL as the connector endpoint. No authentication.

ChatGPT · Settings → Connectors → Create (developer mode) → MCP server URL

https://api.skillsregistry.net/mcp

Authentication: none. Works in chat and deep research — the server exposes the connector search and fetch tools.

Codex CLI · ~/.codex/config.toml

[mcp_servers.skillsregistry]
url = "https://api.skillsregistry.net/mcp"