CodeContextMCP

Created By
offekaa year ago
An MCP server for adding additional repos context using the MCP protocol
Overview

what is CodeContextMCP?

CodeContextMCP is an MCP server designed to enhance the context of additional repositories using the MCP protocol.

how to use CodeContextMCP?

To use CodeContextMCP, set up the server and configure it to connect with your repositories, allowing it to provide contextual information based on the MCP protocol.

key features of CodeContextMCP?

  • Integration with multiple repositories for enhanced context
  • Utilization of the MCP protocol for seamless communication
  • Customizable server settings for specific repository needs

use cases of CodeContextMCP?

  1. Providing contextual information for code reviews across multiple repositories.
  2. Enhancing developer productivity by offering relevant context during coding sessions.
  3. Facilitating better collaboration among teams working on interconnected projects.

FAQ from CodeContextMCP?

  • What is the MCP protocol?

The MCP protocol is a method for servers to communicate and share context about repositories effectively.

  • Is CodeContextMCP free to use?

Yes! CodeContextMCP is open-source and free for everyone to use.

  • How can I contribute to CodeContextMCP?

You can contribute by submitting issues or pull requests on the GitHub repository.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
offeka
Star
0
Language
-
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