DevContext

Created By
Alfredo Urdanetaa year ago
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. The server operates with a database instance dedicated to a single project, eliminating cross-project complexity and ensuring performance with minimal resource requirements. DevContext builds a comprehensive understanding of your codebase - from repository structure down to individual functions - while continuously learning from and adapting to your development patterns.
Overview

What is DevContext?

DevContext is a state-of-the-art context management system for software development, implementing the Model Context Protocol (MCP) with advanced context retrieval techniques. It enhances development workflows by providing intelligent context awareness, understanding codebases, conversations, and development patterns.

How to use DevContext?

To use DevContext, install the necessary dependencies, configure your TursoDB database, and run the server using Node.js. Follow the setup steps outlined in the documentation to integrate it into your development environment.

Key features of DevContext?

  • Intelligent context retrieval with multi-factor relevance scoring
  • Project-level understanding of code structure and relationships
  • Continuous learning from development patterns and conversations
  • Automatic topic segmentation for conversation continuity
  • Development timeline recording significant events
  • Purpose-aware responses tailored to conversation context
  • Low resource requirements for optimal performance
  • Single-file deployment for easy integration

Use cases of DevContext?

  1. Enhancing code review processes with relevant context
  2. Assisting in debugging by providing historical context
  3. Streamlining project management through continuous context awareness

FAQ from DevContext?

  • Can DevContext be used with any programming language?

Yes! DevContext supports multiple languages including JavaScript, Python, Java, and more.

  • Is DevContext free to use?

Yes! DevContext is open-source and free to use under the MIT License.

  • What are the system requirements for running DevContext?

DevContext requires Node.js 18.0.0 or higher and a TursoDB account or compatible SQLite database.

Server Config

{
  "mcpServers": {
    "cursor10x-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "devcontext@latest"
      ],
      "enabled": true,
      "env": {
        "TURSO_DATABASE_URL": "your-turso-database-url",
        "TURSO_AUTH_TOKEN": "your-turso-auth-token"
      }
    }
  }
}
Project Info
Created At
a year ago
Updated At
a year ago
Author Name
Alfredo Urdaneta
Star
-
Language
-
License
-
Category

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago