Optimist MCP Server
An intelligent code optimization MCP server that analyzes and improves codebases across multiple dimensions including performance, memory, code smells, and complexity.
README
Optimist MCP Server
An intelligent code optimization MCP server that analyzes and improves codebases across multiple dimensions
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
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
- Restart your MCP client
- Look for "optimist" in the available tools
- 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.
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。