Skip to main content
Glama
Optimist MCP Server

Optimist MCP Server

by Atomic-Germ

Optimist MCP Server

An intelligent code optimization MCP server that analyzes and improves codebases across multiple dimensions

License: MIT TypeScript MCP CI/CD

Overview

Optimist is a Model Context Protocol (MCP) server designed to work alongside other development tools to provide comprehensive codebase optimization. It analyzes code for performance bottlenecks, memory issues, code smells, and maintainability concerns, offering actionable suggestions for improvement.

Key Features

  • šŸš€ Performance Analysis - Identify bottlenecks and hot paths

  • šŸ’¾ Memory Optimization - Detect leaks and inefficient allocations

  • šŸ“Š Code Quality Metrics - Complexity analysis and maintainability scoring

  • šŸ” Dead Code Detection - Find and eliminate unused code

  • šŸ“¦ Dependency Management - Optimize and analyze dependency graphs

  • šŸŽÆ Smart Refactoring - AI-powered refactoring suggestions

  • šŸ”— MCP Integration - Seamless integration with other MCP tools

  • āœ… Test-Driven - Built using TDD methodology

Related MCP server: code-graph-mcp

Quick Start

Prerequisites

  • Node.js 18+

  • npm or pnpm

  • An MCP-compatible client (e.g., Claude Desktop)

  • A codebase to analyze

Installation

# Clone the repository
git clone https://github.com/Atomic-Germ/mcp-optimist.git
cd mcp-optimist
npm install
npm run build

Test the Server

# Run tests to verify everything works
npm test

# Run with coverage
npm run test:coverage

# Verify build output
ls -la dist/

Configure MCP Client

Claude Desktop

Edit your configuration file:

  • macOS: ~/Library/Application Support/Claude/claude_desktop_config.json

  • Windows: %APPDATA%\Claude\claude_desktop_config.json

  • Linux: ~/.config/claude/claude_desktop_config.json

Add the server:

{
  "mcpServers": {
    "optimist": {
      "command": "node",
      "args": ["/absolute/path/to/mcp-optimist/dist/index.js"],
      "env": {}
    }
  }
}

Verify Setup

  1. Restart your MCP client

  2. Look for "optimist" in the available tools

  3. You should see 8 optimization tools available

First Code Analysis

Try these examples in your MCP client:

Analyze Code Complexity

Use analyze_complexity tool on your project:
Path: "./src"
Max Complexity: 10
Report Format: "summary"

Detect Performance Issues

Use analyze_performance tool:
Path: "./src"
Include Tests: false
Threshold: "medium"

Find Code Smells

Use detect_code_smells tool:
Path: "./src"
Severity: "medium"

Memory Analysis

Use optimize_memory tool:
Path: "./src"
Detect Leaks: true
Suggest Fixes: true

Development

Development Commands

# Development
npm run dev              # Run with ts-node (development mode)
npm run build:watch      # Auto-rebuild on changes

# Testing
npm test                 # Run all tests
npm run test:watch       # Watch mode for tests
npm run test:coverage    # Generate coverage report

# Code Quality
npm run lint             # Check code with ESLint
npm run lint:fix         # Auto-fix linting issues
npm run format           # Format code with Prettier
npm run format:check     # Check formatting

# Build
npm run build            # Compile to dist/
npm run clean            # Remove dist/

Project Structure

mcp-optimist/
ā”œā”€ā”€ src/
│   ā”œā”€ā”€ index.ts         # MCP server entry point
│   ā”œā”€ā”€ server.ts        # OptimistServer class
│   ā”œā”€ā”€ types/           # TypeScript definitions
│   ā”œā”€ā”€ tools/           # Tool implementations
│   ā”œā”€ā”€ analyzers/       # Analysis engines
│   └── utils/           # Utility functions
│
ā”œā”€ā”€ tests/
│   ā”œā”€ā”€ unit/            # Unit tests
│   ā”œā”€ā”€ integration/     # Integration tests
│   └── fixtures/        # Test fixtures
│
ā”œā”€ā”€ docs/                # Documentation
ā”œā”€ā”€ archive/             # Archived documentation
ā”œā”€ā”€ README.md            # This file
ā”œā”€ā”€ package.json         # Dependencies and scripts
ā”œā”€ā”€ tsconfig.json        # TypeScript configuration
ā”œā”€ā”€ jest.config.js       # Test configuration
ā”œā”€ā”€ eslint.config.js     # Linting rules
ā”œā”€ā”€ .prettierrc          # Code formatting
└── dist/                # Compiled JavaScript

Examples

Basic Project Analysis

Perform comprehensive analysis of your entire project:

// Analyze overall code quality
{
  tool: "detect_code_smells",
  arguments: {
    path: "./src",
    severity: "medium"
  }
}

// Check performance issues
{
  tool: "analyze_performance",
  arguments: {
    path: "./src",
    threshold: "medium",
    includeTests: false
  }
}

// Find complexity issues
{
  tool: "analyze_complexity",
  arguments: {
    path: "./src",
    maxComplexity: 8,
    reportFormat: "detailed"
  }
}

Single File Analysis

Analyze a specific problematic file:

{
  tool: "analyze_performance",
  arguments: {
    path: "./src/services/dataProcessor.ts",
    threshold: "low",
    profileHotPaths: true,
    trackAsyncOperations: true
  }
}

Memory Optimization

Find and fix memory leaks in a React component:

{
  tool: "optimize_memory",
  arguments: {
    path: "./src/components",
    detectLeaks: true,
    analyzeClosures: true
  }
}

Leak Analysis Result:

{
  data: {
    findings: [
      {
        type: 'event-listener-leak',
        file: 'src/components/DataChart.tsx',
        line: 23,
        description: 'Event listeners not cleaned up in useEffect',
        leakPotential: 'high',
      },
      {
        type: 'closure-retention',
        file: 'src/hooks/useDataFetch.ts',
        line: 15,
        description: 'Closure retaining large objects unnecessarily',
      },
    ];
  }
}

Memory Leak Fixes:

Problem - Event Listener Leak:

// Problematic - no cleanup
function DataChart() {
  useEffect(() => {
    window.addEventListener('resize', handleResize);
    // Missing cleanup function
  }, []);
}

Fixed:

// Fixed with proper cleanup
function DataChart() {
  useEffect(() => {
    const handleResize = () => {
      // Handle resize
    };

    window.addEventListener('resize', handleResize);

    // Cleanup function prevents leak
    return () => {
      window.removeEventListener('resize', handleResize);
    };
  }, []);
}

Performance Optimization

Identify and fix performance bottlenecks:

{
  tool: "analyze_performance",
  arguments: {
    path: "./src/services/dataProcessor.ts",
    threshold: "low",
    profileHotPaths: true
  }
}

Before (Problematic):

// O(n²) complexity - problematic
function processLargeDataset(items: Item[], lookup: LookupItem[]): ProcessedItem[] {
  return items.map((item) => {
    // Inner loop for each item - O(n²)
    const match = lookup.find((l) => l.id === item.lookupId);
    return { ...item, enrichedData: match?.data };
  });
}

After (Optimized):

// O(n) complexity - optimized
function processLargeDataset(items: Item[], lookup: LookupItem[]): ProcessedItem[] {
  // Create lookup map once - O(n)
  const lookupMap = new Map(lookup.map((l) => [l.id, l.data]));

  // Single pass through items - O(n)
  return items.map((item) => ({
    ...item,
    enrichedData: lookupMap.get(item.lookupId),
  }));
}

Code Quality Analysis

Analyze function complexity and code smells:

{
  tool: "analyze_complexity",
  arguments: {
    path: "./src/utils/validation.ts",
    maxComplexity: 6,
    includeCognitive: true
  }
}

{
  tool: "detect_code_smells",
  arguments: {
    path: "./src/services/UserService.ts",
    severity: "high"
  }
}

For more examples, see the API Reference.

Available Tools

8 tools
analyze_complexityC

Evaluate cyclomatic and cognitive complexity

Inputs: path (required), reportFormat, maxComplexity.

analyze_dependenciesB

Map and analyze dependency graphs

Inputs: path (required), checkCircular, suggestUpdates.

analyze_performanceC

Analyze code performance and identify bottlenecks

Inputs: path (required), threshold, includeTests.

detect_code_smellsC

Identify anti-patterns and code quality issues

Inputs: path (required), severity.

find_dead_codeC

Identify and locate unused code

Inputs: path (required).

optimize_hot_pathsC

Analyze and optimize frequently executed code paths

Inputs: path (required), profilingData.

optimize_memoryC

Detect memory leaks and suggest memory-efficient patterns

Inputs: path (required), detectLeaks, suggestFixes.

suggest_refactoringC

Provide AI-powered refactoring recommendations

Inputs: path (required), focusArea, maxResults, minPriority, +1 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.4/5.0

    Scored across 8 tools

    Disambiguation4/5

    Most tools target clearly distinct concerns: complexity, code smells, dead code, dependencies, memory, and refactoring. The only point of confusion is between analyze_performance and optimize_hot_paths, both of which deal with performance bottlenecks and could be misselected by an agent.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern using clear action verbs (analyze, optimize, detect, find, suggest). The convention is uniform and predictable, making it easy to infer the purpose of each tool from its name.

    Tool Count5/5

    With 8 tools, the server is well-scoped for a code analysis and optimization domain. Each tool covers a distinct aspect of the problem space without unnecessary bloat or redundancy.

    Completeness4/5

    The tool surface covers the major dimensions of code quality: performance, memory, complexity, smells, dead code, dependencies, and refactoring. A minor gap is the lack of a tool to directly apply or validate changes, but the server's analytical focus is well served by the existing set.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers