1. Conduid
  2. Developer Tools
  3. Cursor Chat History MCP
MCP server · Developer Tools

Cursor Chat History MCP

by · github.com/vltansky/cursor-chat-history-mcp
Unclaimed last commit 9 months ago devtools
InstallView source
35Low

Scored a month ago · breakdown

About Cursor Chat History MCP

Cursor Chat History MCP is an MCP server published by vltansky in the Developer Tools category.

The repository has 33 stars and 11 forks, with the last commit 9 months ago. Six months or more without a commit doesn't mean the server is broken, but check the open issues before depending on it in production.

Install

From source
git clone https://github.com/vltansky/cursor-chat-history-mcp

This server has no ConduID identity, so agent calls to it are not receipted. Pin the version you install and review the source before granting it credentials.

Tools (4)

get_commit_conversationsFind conversations linked to a commit

Parameters not published.

get_file_contextGet conversations and commits related to a file

Parameters not published.

link_conversation_commitManually link conversation ↔ commit

Parameters not published.

list_conversation_commitsFind commits linked to a conversation

Parameters not published.

Ask AI

✦

Ask AI about Cursor Chat History MCP

Powered by Claude · Grounded in docs

I know everything about Cursor Chat History MCP. Ask me about installation, configuration, usage, or troubleshooting.

Security checks

6 checks have not been run yet.

Questions

About Cursor Chat History MCP

How do I install Cursor Chat History MCP?

No package has been published for this server, so install it from source: clone the repository and follow its README.

Is Cursor Chat History MCP safe to use with an AI agent?

Its trust score is 35 out of 100 (low). Conduid hasn't run static security checks on this repository yet, so review the source yourself before granting it credentials. It has no ConduID identity yet, so agent calls to it are not receipted.

Is Cursor Chat History MCP still maintained?

The last commit was 9 months ago. That's long enough that you should check whether the maintainer is responding to issues before depending on it.