Change Analyzer MCP Server

What is Change Analyzer MCP Server?

An Agent-to-Agent (A2A) compatible server for Git repository analysis. It provides metrics, statistics, and directory structure insights, and integrates with agents via the A2A protocol.

How to use Change Analyzer MCP Server?

Requires Python 3.9+ and Redis for state management. Install via pip install mcp-change-analyzer or from source. Start the server with mcp-change-analyzer serve --config config/server.yaml. Send A2A requests to the server’s RPC endpoint using an A2A client.

Key features of Change Analyzer MCP Server

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

Use cases of Change Analyzer MCP Server

• Monitor code changes in a Git repository over time
• Generate summary metrics for project health reports
• Examine directory structure for refactoring or migration planning
• Enable AI agents to query repository state via the A2A protocol

FAQ from Change Analyzer MCP Server

What are the prerequisites for running the server?

You need Python 3.9 or later and Redis (for state management).

How do I install and start the server?

Install with pip install mcp-change-analyzer or clone the source and run pip install -e .. Start with mcp-change-analyzer serve --config config/server.yaml.

How is the server configured?

Configuration is done via YAML files; an example is provided at config/server.yaml.

How do agents communicate with the server?

Agents use the A2A protocol by sending requests to the server’s RPC endpoint. An example Python client is shown in the README.

Does the server require a database or external service?

Yes, Redis is required for state management. The server does not store data permanently beyond what is in the Redis instance.