MCP Tools MCP Server

MCP Tools - Multi-Server Architecture

A modular FastMCP server architecture providing development tools, analytics, and reporting for Claude Code integration.

🏗️ Architecture Overview

MCP Tools uses a multi-server composition architecture with three specialized servers:

• 🎯 Coordinator (localhost:8002) - Main orchestration server that composes tools and reports
• 🛠️ Tools (localhost:8003) - Development workflow automation (PR analysis, code review, JIRA)
• 📈 Reports (localhost:8004) - Performance analytics and reporting (quarterly reports, metrics)

All servers can run independently or composed together through the coordinator using FastMCP's mount() pattern.

🚀 Quick Start

Container-First Deployment (Recommended)

# Start all services
./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

Development Setup

# Install dependencies
poetry install

# Run coordinator (mounts all servers)
poetry run python coordinator/server.py

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

📊 Service Endpoints

🛠️ Available Tools (14 Core Tools)

Development Workflow Tools (Tools Server)

1. PR Health (`pr_health`)

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

• Input: GitHub PR URL, optional description
• Output: Comprehensive health analysis with actionable solutions
• Example: "pr_health https://github.com/owner/repo/pull/123"

2. Code Review (`code_review`)

Performs comprehensive code quality review with security and performance analysis.

• Input: GitHub PR URL, optional focus area, max diff lines
• Output: Structured code quality assessment
• Example: "code_review https://github.com/owner/repo/pull/123 security"

3. Tech Design Review (`tech_design_review`)

Reviews technical design documents with architecture and implementation analysis.

• Input: Document URL (Confluence/GitHub), optional focus area
• Output: Design review with architecture recommendations
• Example: "tech_design_review https://company.atlassian.net/wiki/pages/123456"

4. JIRA Transition (`jira_transition`)

Automates JIRA workflow transitions with intelligent state management.

• Input: Ticket ID, target state (supports aliases: "dev", "review", "qa", "done")
• Output: JIRA transition instructions with Atlassian MCP integration
• Example: "jt SI-1234 start" or "jira_transition SI-1234 development"

5. Get JIRA Transitions (`get_jira_transitions`)

Calculates optimal transition paths between JIRA statuses.

• Input: From status, optional to status
• Output: Step-by-step transition path with MCP commands
• Example: "get_jira_transitions 'Open' 'In Development'"

6. Epic Status Report (`epic_status_report`)

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

• Input: Epic ticket ID, optional focus area
• Output: Epic progress analysis with assignee action items
• Example: "epic_status_report SI-9038"

Analytics & Reporting Tools (Reports Server)

7. Quarterly Team Report (`quarterly_team_report`)

Generates comprehensive quarterly team performance reports with anonymized metrics.

• Input: Team prefix, year, quarter, optional description
• Output: Team analysis using JIRA and GitHub data
• Example: "quarterly_team_report SI 2025 2"

8. Quarter-over-Quarter Analysis (`quarter_over_quarter_analysis`)

Analyzes team performance trends and size changes across multiple quarters.

• Input: Team prefix, period (e.g., "2024", "2023-2025")
• Output: Multi-quarter trend analysis with team composition tracking
• Example: "quarter_over_quarter_analysis SI 2024"

9. Personal Quarterly Report (`personal_quarterly_report`)

Generates individual contributor performance reports for personal development.

• Input: Team prefix, year, quarter
• Output: Personal performance analysis with growth recommendations
• Example: "personal_quarterly_report SI 2025 2"

10. Personal Quarter-over-Quarter (`personal_quarter_over_quarter`)

Analyzes personal performance trends and growth across multiple time periods.

• Input: Team prefix, period
• Output: Personal growth analysis with development insights
• Example: `"personal_quarter_over_qua