mcp_cursor10x_initConversationLABSCO SUMMARY
One call at the start of a turn, and the assistant knows where you left off.
The design point is mcp_cursor10x_initConversation: instead of assembling memory by hand, one call stores the incoming message and returns recent conversation, active files and long-term memory together. Decisions and requirements are stored separately from chat history, so the things that should survive a session are not competing with the things that should not.
What it is
A server that stores conversation history, active files, project decisions and vector-embedded code context in a database, and hands the relevant parts back when a session starts.
What you get
- mcp_cursor10x_initConversation — one call at the start of a turn that stores the user's message and returns the assembled context
- mcp_cursor10x_getComprehensiveContext — recent messages, active files and long-term memory gathered into one payload
- mcp_cursor10x_endConversation — close out a session with the assistant's message and a summary
- Short-term memory — mcp_cursor10x_storeUserMessage, mcp_cursor10x_storeAssistantMessage and mcp_cursor10x_getRecentMessages
- Active files — mcp_cursor10x_trackActiveFile and mcp_cursor10x_getActiveFiles, so the assistant knows what the work has been touching
- Long-term memory — mcp_cursor10x_storeMilestone, mcp_cursor10x_storeDecision and mcp_cursor10x_storeRequirement
- Episodic memory — mcp_cursor10x_recordEpisode and mcp_cursor10x_getRecentEpisodes for a chronological record of actions
- mcp_cursor10x_manageVector for vector-embedded content, giving semantic recall of related code and text rather than exact matching
- mcp_cursor10x_checkHealth and mcp_cursor10x_getMemoryStats for whether the store is reachable and what is in it
- Importance levels on stored items, so the retrieved context is ranked rather than dumped
Requirements
A Turso database with its URL and an auth token, handed to the server at launch; the schema is created for you on first run. Runs under Node. The README now opens by announcing that Cursor10x has evolved into DevContext, which is worth reading about before you commit to this one.
Setup effort
One command plus a key — npx cursor10x-mcp, then supply credentials
USE CASES
Picking up where a session left off
Open the turn with the initialise call and get recent messages, active files and stored decisions back in one payload.
Not re-arguing a decision you already made
Store the decision when it is made, and let it come back with the context next time.
Keeping track of which files the work touches
Record each active file as it is opened and read the list back at the start of the next session.
Finding related code by meaning rather than by name
Store embedded content and search it semantically instead of grepping for a string.
Checking the memory is actually working
Run the health check and read the statistics on what has been stored.
17 tools
Listed in project docs. Your client may show a different list.
mcp_cursor10x_endConversationmcp_cursor10x_checkHealthmcp_cursor10x_getMemoryStatsmcp_cursor10x_getComprehensiveContextmcp_cursor10x_storeUserMessagemcp_cursor10x_storeAssistantMessagemcp_cursor10x_trackActiveFilemcp_cursor10x_getRecentMessagesmcp_cursor10x_getActiveFilesmcp_cursor10x_storeMilestonemcp_cursor10x_storeDecisionmcp_cursor10x_storeRequirementmcp_cursor10x_recordEpisodemcp_cursor10x_getRecentEpisodesmcp_cursor10x_manageVectormcp_cursor10x_generateBannerBEFORE YOU INSTALL
What to know first
Tools you get
17 tools named in the project's documentation.
Requires
- npx on PATH
- Node.js 18 or later
- TURSO_AUTH_TOKEN in your environment
- TURSO_DATABASE_URL in your environment
Where it runs
The documented client runs the server on your machine.
INSTALLATION
Connect your client
Server setup
npx cursor10x-mcpMCP Clients
Cursor
{
"mcpServers": {
"cursor10x-mcp": {
"command": "npx",
"args": [
"cursor10x-mcp"
],
"enabled": true,
"env": {
"TURSO_DATABASE_URL": "<YOUR_TURSO_DATABASE_URL>",
"TURSO_AUTH_TOKEN": "<YOUR_TURSO_AUTH_TOKEN>"
}
}
}
}