finalize_conversation_contextLABSCO SUMMARY
Project memory that lives in your own database rather than a vendor's.
Retrieval is keyword, relationship-graph and metadata driven, so nothing has to be embedded or re-indexed offline and all processing stays local. The trade is scope: one database per project, and the full benefit comes from opening and closing the session properly rather than calling tools ad hoc.
What it is
A context server dedicated to one project. It opens a conversation with a snapshot of the codebase, takes updates as files and messages accumulate, answers targeted questions about the project, records milestones, and closes the session with what it learned — all held in a SQL database of your own.
What you get
- A session that opens with architectural context, recent changes and prior conversations, at the depth you ask for
- Context kept current as code changes and new messages come in, including across a shift in topic
- Snippets pulled for one specific question, filtered by entity type or file path
- Milestones recorded when a feature lands or an architectural call is made, with an impact assessment
- A closing pass that extracts learnings and suggests next steps
- Retrieval driven by keywords, relationship graphs and structured metadata rather than embeddings, so there is no model to host
Requirements
A SQL database of your own — the server is built for Turso and takes its URL and an access token as environment settings. One database per project; the schema is created and maintained on first run. Runs under Node.
Setup effort
One command plus a key — npx -y devcontext@latest, then supply credentials
USE CASES
01
Starting a session without re-explaining the project
Open the conversation with a context snapshot — architecture, recent changes, prior discussion — and choose how deep it should go.
02
Keeping the assistant current as you edit
Feed new messages and changed files back in as you work, so later answers reflect what you just did rather than the state at session start.
03
Asking a pointed question about your own codebase
Query for the part you care about and get the relevant snippets back, narrowed to the entity types or file paths you name.
04
Marking the decisions worth remembering
Record a landed feature or an architectural call so it is still in scope in a session next week.
05
Closing out a working session
Wrap up in one call and get the summary, the extracted learnings and the suggested next steps together.
5 tools
Counted once with only startup setup. Other versions, modes or optional credentials may expose a different list.
initialize_conversation_contextrecord_milestone_contextretrieve_relevant_contextupdate_conversation_contextBEFORE YOU INSTALL
What to know first
Tools you get
5 tools when we connected. Call initialize_conversation_context once first and finalize_conversation_context once last; the other tools need the conversationId it returns.
Requires
- npx on PATH
- Node.js Runtime environment
- Node.js 18 or later
- TURSO_DATABASE_URL in your environment
- TURSO_AUTH_TOKEN in your environment
CONTEXT COST
Light Standing cost
Rated by the size of the 5 tool definitions that ride along on every turn, not by how many there are
INSTALLATION
Connect your client
Server setup
TERMINAL
npx -y devcontext@latestMCP Clients
Cursor
CURSOR · JSON
{
"mcpServers": {
"devcontext": {
"command": "npx",
"args": [
"-y",
"devcontext@latest"
],
"enabled": true,
"env": {
"TURSO_DATABASE_URL": "<YOUR_TURSO_DATABASE_URL>",
"TURSO_AUTH_TOKEN": "<YOUR_TURSO_AUTH_TOKEN>"
}
}
}
}.cursor/mcp.json in your project directory
Cursor — with Context7
CURSOR — WITH CONTEXT7 · JSON
{
"mcpServers": {
"devcontext": {
"command": "npx",
"args": [
"-y",
"devcontext@latest"
],
"enabled": true,
"env": {
"TURSO_DATABASE_URL": "libsql://<YOUR_PROJECT_DB_NAME_TURSO>",
"TURSO_AUTH_TOKEN": "<YOUR_TURSO_AUTH_TOKEN>"
}
},
"context7": {
"command": "npx",
"args": [
"-y",
"@upstash/context7-mcp@latest"
]
}
}
}
