Practical overview
When it fits
Use DevContext when a Cursor-based development workflow needs project-scoped memory that can carry conversation history and code context between sessions.
Who it is for
- Developers using Cursor who want an assistant to retain project context across sessions.
- Developers configuring an MCP server and Turso-backed storage for a project.
Documented uses
- Carry conversation messages, active files, decisions, and milestones into later development sessions.
- Retrieve semantically related code or project context rather than relying only on exact text.
- Track relationships between code structures across files.
- Initialize a conversation by storing a message and returning a banner and context for the assistant.
Requirements & limits
The repository is public and specifies an MIT license. The documented installation requires Node.js 18 or higher, npm or yarn, and a Turso database account.
- The documented configuration connects the MCP server to Turso using a database URL and authentication token.
- The repository describes a one-database-per-project design.
- Its documented memory model combines recent, long-term, episodic, and semantic context.
- The concrete setup instructions configure Cursor through a project-level .cursor/mcp.json file.
Check current requirements in the official documentation. Source-based guidance does not mean OpenViST has run or independently tested this project.
Set up DevContext as a Cursor MCP server
Prepare a Turso database and configure a project-level Cursor MCP entry for DevContext.
Before you start
- Node.js 18 or higher
- npm or yarn
- A Turso database account
Steps
Create a Turso database and obtain its database URL and authentication token.
In the project directory, add the documented MCP server entry to .cursor/mcp.json.
Set TURSO_DATABASE_URL and TURSO_AUTH_TOKEN in that entry and configure it to launch cursor10x-mcp with npx.
Expected outcome
The project-level Cursor configuration specifies the DevContext MCP server and its Turso connection credentials.
Guide limitations
- These steps describe setup only; they do not establish that the configuration has been run or verified.
- The documented setup requires a Turso account and does not describe a database-free configuration.
Sources & review
Source record details
- Source availability
- Active
- Sources checked
- 17 October 2026
- Original website title
- aiurda/cursor10x-mcp · Official homepage title · retained in its source language

