CodeCompass

Created By
alvinveroya year ago
CodeCompass: AI-powered Vibe Coding with MCP. Connects Git repositories to AI assistants like Claude, using Ollama for privacy or OpenAI for cloud. Integrates with VSCode, Cursor, and more.
Overview

what is CodeCompass?

CodeCompass is an AI-powered Node.js MCP server designed for Git repository analysis, transforming your codebase into an AI-driven knowledge base that enhances coding efficiency and reduces errors.

how to use CodeCompass?

To use CodeCompass, you can either clone the repository and install dependencies or run it directly using npx with your local Git repository path.

key features of CodeCompass?

  • Codebase Analysis: Indexes Git repositories and stores code/docs in Qdrant.
  • AI-Driven Context: Generates context-aware prompts with code summaries and documentation.
  • Diff Tracking: Keeps track of repository updates with timestamps.
  • Developer Tools: Provides resources and tools for searching code and generating suggestions.

use cases of CodeCompass?

  1. Streamlining coding processes for developers.
  2. Reducing errors in code by providing context-aware suggestions.
  3. Gaining insights into project structure and documentation.

FAQ from CodeCompass?

  • What are the prerequisites for using CodeCompass?

You need Node.js (v20+), Docker for Qdrant, and Ollama with specific models.

  • Is CodeCompass open-source?

Yes! CodeCompass is MIT-licensed and open-source.

  • How can I contribute to CodeCompass?

Contributions are welcome! Please refer to the CONTRIBUTING.md file in the repository.

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