DevContext: Autonomous Context Awareness Model-Context-Protocol (MCP) Server

Created By
aurda012a 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 and delivers highly relevant context providing a deeper understanding of your codebase.
Overview

What is DevContext?

DevContext is an advanced Model Context Protocol (MCP) server that provides developers with continuous, project-centric context awareness, adapting to their development patterns to enhance understanding of their codebase.

How to use DevContext?

To use DevContext, set up a TursoDB database, configure the MCP in your IDE, and implement the Cursor Rules for autonomous context management and task integration.

Key features of DevContext?

  • Continuous learning from development patterns
  • Project-centric context management
  • Integration with Cursor IDE for task management
  • Autonomous documentation retrieval and context awareness

Use cases of DevContext?

  1. Enhancing code comprehension during development.
  2. Streamlining task management workflows.
  3. Providing relevant context during code reviews and discussions.

FAQ from DevContext?

  • Can DevContext be used with any IDE?

Yes, DevContext can be configured to work with any IDE that supports the Model Context Protocol.

  • Is there a cost associated with using DevContext?

DevContext is free to use, but requires a TursoDB account for database management.

  • How does DevContext ensure data security?

Each project uses a dedicated database instance, and credentials are managed securely through environment variables.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
aurda012
Star
14
Language
HTML
License
MIT license

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