Change Analyzer MCP Server

Created By
manavgupa year ago
MCP Server for analyzing outstanding changes to a repo
Overview

what is Change Analyzer MCP Server?

Change Analyzer MCP Server is an Agent-to-Agent (A2A) compatible server designed for analyzing outstanding changes in Git repositories.

how to use Change Analyzer MCP Server?

To use the Change Analyzer MCP Server, install it via pip or from the source, start the server, and send A2A requests to analyze repositories.

key features of Change Analyzer MCP Server?

  • Analyze Git repositories for changes
  • Provide metrics and statistics about repositories
  • Analyze directory structures
  • A2A protocol integration for agent communication

use cases of Change Analyzer MCP Server?

  1. Monitoring changes in a collaborative Git repository.
  2. Generating statistics for repository performance.
  3. Analyzing directory structures for better organization.

FAQ from Change Analyzer MCP Server?

  • What are the prerequisites for using Change Analyzer MCP Server?

You need Python 3.9+ and Redis for state management.

  • How do I start the server?

You can start the server using the command: mcp-change-analyzer serve --config config/server.yaml.

  • Can I use it with any Git repository?

Yes! It is designed to work with any Git repository.

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