DevContext is a cutting-edge Model Context Protocol (MCP) server designed to provide developers with continuous, project-centric context awareness.
DevContext is a cutting-edge Model Context Protocol (MCP) server designed to provide developers with continuous, project-centric context awareness.
DevContext is a cutting-edge Model Context Protocol (MCP) server designed to provide developers with continuous, project-centric context awareness. Unlike traditional context systems, DevContext continuously learns from and adapts to your development patterns. DevContext leverages sophisticated retrieval methods, focusing on keyword analysis, relationship graphs, and structured metadata to deliver highly relevant context during development, understanding both your conversations and your codebase at a deeper level.
initialize_conversation_context — Initializes a new conversation session with comprehensive project context.update_conversation_context — Updates the active context with new messages and code changes.retrieve_relevant_context — The retrieve_relevant_context tool exposed by this server.record_milestone_context — Records significant development milestones for future reference.finalize_conversation_context — Concludes a conversation, extracting learnings and suggesting next steps.Compare MCP servers by category, or browse hosted MCP servers if you prefer an endpoint over a local process.
Check the linked publisher documentation and your connected client's tool list. Names and availability can vary with the server version and account permissions.
| Tool | What it does |
|---|---|
| initialQuery | The user's first message or question |
| contextDepth | Minimal, standard, or comprehensive context depth |
| includeArchitecture | Whether to include architectural context |
| focusHint | Optional focus on specific code entity |
| conversationId | ID from initialize_conversation_context |
| newMessages | New messages exchanged since last update |
| codeChanges | Code files created or modified |
| preserveContextOnTopicShift | Whether to maintain context during topic changes |
| query | Specific question about the project |
| constraints | Optional filters for entity types, file paths, etc. |
| weightingStrategy | How to prioritize results |
| milestoneCategory | Category (feature, bug fix, refactoring, etc.) |
| assessImpact | Whether to analyze impact |
| extractLearnings | Whether to identify and extract learnings |
| promotePatterns | Whether to promote patterns to global repository |
| generateNextSteps | Whether to suggest follow-up actions |
| initialize_conversation_context | |
| update_conversation_context | |
| retrieve_relevant_context | |
| record_milestone_context | |
| finalize_conversation_context |
{
"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"
}
}
}
}From the project documentation. Replace placeholders and example paths before connecting.
| Variable | Description | Required |
|---|---|---|
| TURSO_DATABASE_URL | Declared in the maintainer’s client configuration. | Yes |
| TURSO_AUTH_TOKEN | Declared in the maintainer’s client configuration. | Yes |
Read, search and edit files inside allowed directories with the Model Context Protocol reference Filesystem server.
Retrieve version-aware library documentation and code examples with Context7 MCP, using resolve-library-id and query-docs.
Use Microsoft’s Playwright MCP server to navigate pages, inspect accessibility snapshots, fill forms and capture browser screenshots.
Connect GitHub MCP to repositories, issues and pull requests with GitHub’s hosted service or a locally run server.
Use the Supabase MCP server to inspect database schemas, query project data and retrieve docs through a project-scoped connection.
Search Linear issues and projects, inspect work context and manage updates through Linear’s hosted MCP server with OAuth.