Cursor10x MCP Server

Cursor10x MCP becomes available to MCP clients through the cursor10x mcp mcp server. Memory System for Cursor using MCP - Provides persistent context awareness for Claude.

What Cursor10x MCP does

🧠 Project-Centric 📊 Relationship Graphs ⚡ High Performance One database per project Intelligent code connections Minimal resource needs

The Cursor10x Memory System creates a persistent memory layer for AI assistants (specifically Claude), enabling them to retain and recall:

Key capabilities

• Persistent Context — Maintains conversation and project context across multiple sessions
• Importance-Based Storage — Prioritizes information based on configurable importance levels
• Multi-Dimensional Memory — Combines short-term, long-term, episodic, and semantic memory systems
• Comprehensive Retrieval — Provides unified context from all memory subsystems
• Health Monitoring — Includes built-in diagnostics and status reporting
• Banner Generation — Creates informative context banners for conversation starts
• Database Persistence — Stores all memory data in Turso database with automatic schema creation
• Vector Embeddings — Creates numerical representations of text and code for similarity search

Tools it exposes

Once connected, the assistant can call these 14 tools directly:

• Prerequisites — The Prerequisites tool exposed by this server
• mcp_cursor10x_initConversation — Initializes a conversation by storing the user message, generating a banner, and retrieving context in one operation. This unified tool replaces the need for
• mcp_cursor10x_endConversation — Ends a conversation by combining multiple operations in one call: storing the assistant's final message, recording a milestone for what was accomplished, and
• mcp_cursor10x_checkHealth — Checks the health of the memory system and its database connection
• mcp_cursor10x_getMemoryStats — The mcp_cursor10x_getMemoryStats tool exposed by this server
• mcp_cursor10x_getComprehensiveContext — Retrieves a unified context from all memory subsystems, combining short-term, long-term, and episodic memory
• mcp_cursor10x_storeUserMessage — The mcp_cursor10x_storeUserMessage tool exposed by this server
• mcp_cursor10x_storeAssistantMessage — Stores an assistant message in the short-term memory system
• mcp_cursor10x_trackActiveFile — Tracks an active file being accessed or modified by the user
• mcp_cursor10x_getRecentMessages — The mcp_cursor10x_getRecentMessages tool exposed by this server
• mcp_cursor10x_getActiveFiles — The mcp_cursor10x_getActiveFiles tool exposed by this server
• mcp_cursor10x_storeMilestone — The mcp_cursor10x_storeMilestone tool exposed by this server
• mcp_cursor10x_storeDecision — The mcp_cursor10x_storeDecision tool exposed by this server
• mcp_cursor10x_storeRequirement — The mcp_cursor10x_storeRequirement tool exposed by this server

Installing the cursor10x mcp mcp server

Setup follows the standard MCP pattern: clone or install the server, then register it in your client's configuration file and restart the client. The configuration snippets on this page cover Claude Desktop, Claude Code and Cursor.

Configuration

Before the server will start you need to supply 2 environment variables: TURSO_DATABASE_URL, TURSO_AUTH_TOKEN. Keep credentials in your client's env block or a secrets manager rather than committing them.

Requirements

• Node.js 18 or higher - npm or yarn package manager - Turso database account

Where it fits

Knowledge and memory servers address the most frustrating trait of language models — walking into every conversation with no recollection of the last one. Cursor10x MCP sits in that group, and the shape of its toolset — Prerequisites, mcp_cursor10x_initConversation, mcp_cursor10x_endConversation among others — tells you what it is really for. Worth comparing against the other knowledge memory servers in this directory before you commit to one, since several overlap in scope but differ sharply in setup cost and permissions.

Practical notes

• This server runs locally, so it operates with whatever access your machine and its credentials already have. Scope that deliberately rather than by default.
• It will not start until its required credentials are present, so set those before wondering why the tools never appear.
• With 14 tools exposed, expect a noticeable bump in prompt size — disable it in projects that never use Cursor10x MCP.
• Maintained by aurda012.
• MCP clients ask for confirmation before each tool call by default. Keep that on while you learn what the cursor10x mcp mcp server actually does with your data.
• Every entry in this directory is reviewed by hand before it goes live, and details are checked against the project's own documentation.