MCP Tools

You are learning to deploy and use MCP Tools, a modular multi-server setup that orchestrates development tools and analytics through a single coordinating interface. You can run the specialized servers independently or mounted together under the coordinator to gain a unified workflow for code analysis, JIRA management, and quarterly reporting, while keeping each component's responsibilities separate for reliability and scalability.

How to use

You interact with MCP Tools through a client or automation that talks to the coordinator endpoint. Use the coordinator as your single entry point to access all tools and reports. When the coordinator mounts the Tools and Reports servers, you can run actions like PR health checks, code reviews, JIRA transitions, and quarterly reports from one place. You can also mount individual servers directly if you prefer a decentralized setup.

How to install

Prerequisites you need to install and run the MCP Tools stack:

• Python 3.11+ must be installed on your system

• Poetry is used to install and run the Python servers

• Container tooling for building and running services

• Version control and repository access

• For health checks and CLI interactions

Step-by-step commands to get started in a development setup:

poetry install
poetry run python coordinator/server.py

# Or run individual servers if you prefer
poetry run python tools/server.py      # Tools server (port 8003)
poetry run python reports/server.py    # Reports server (port 8004)

If you want to run all services through a container workflow, follow the container-first approach and use the provided scripts to start, check status, and stop all services, then add the coordinator endpoint to Claude Code for MCP access.

# Start all services via the container script
./scripts/start.sh

# Check status
./scripts/status.sh

# Stop all services
./scripts/stop.sh

# Add to Claude Code (coordinator endpoint)
claude mcp add mcp-tools http://localhost:8002/mcp/ --transport http --scope user

Configuration and endpoints

The MCP Tools stack consists of three servers that can run independently or be mounted together under the coordinator. Each service exposes a health endpoint to verify availability.

Coordinator (port 8002): health at http://localhost:8002/health and acts as the main composition server.

Tools server (port 8003): health at http://localhost:8003/health and provides development workflows such as PR health, code review, JIRA transitions, and more.

Reports server (port 8004): health at http://localhost:8004/health and provides analytics and quarterly reporting.

Practical usage patterns

Use the coordinator to mount the development tools and reporting capabilities behind a single endpoint. This enables streamlined workflows like triggering a PR health check, performing a security-focused code review, executing a JIRA transition, and generating quarterly reports in a single automation chain.

If you prefer fine-grained control, run the Tools and Reports servers directly in development mode and invoke their endpoints individually. The Commands section shows how to start each server.

Notes and troubleshooting

Health checks are exposed on /health for each service. If a service does not respond, verify that its process is running and that the port is not blocked by a firewall. For container deployments, ensure the orchestrator scripts are executed with the appropriate permissions and that non-root execution is used for security.

Security and best practices

Run servers with a non-root user in production. Use environment-based configuration to avoid hard-coding sensitive information. When integrating with Claude Code or other clients, scope access appropriately and rely on the built-in health endpoints to monitor service status.

Available tools

PR Health

Analyzes PR health including open review threads, CI status, and merge readiness.

Code Review

Performs comprehensive code quality review with security and performance analysis.

Tech Design Review

Reviews technical design documents with architecture and implementation analysis.

JIRA Transition

Automates JIRA workflow transitions with intelligent state management.

Get JIRA Transitions

Calculates optimal transition paths between JIRA statuses.

Epic Status Report

Generates epic status with sub-task analysis and progress tracking.

Quarterly Team Report

Generates quarterly team performance reports using JIRA and GitHub data.

Quarter-over-Quarter Analysis

Analyses performance trends and team composition across quarters.

Personal Quarterly Report

Generates individual contributor performance reports for development.

Personal Quarter-over-Quarter

Analyzes personal growth trends over multiple periods.

Setup Prerequisites

Validates and sets up prerequisites for MCP Tools.

Check Tool Requirements

Checks prerequisites for individual MCP tools.

Echo

Simple connectivity test for MCP communication validation.

Get System Info

System diagnostics and health monitoring.