Improves MCP server performance through connection pooling, load balancing, and registry optimization.
Install
mkdir -p .claude/skills/v3-mcp-optimization && curl -L -o skill.zip "https://agentskills.codes/api/skills/download/7392" && unzip -o skill.zip -d .claude/skills/v3-mcp-optimization && rm skill.zipInstalls to .claude/skills/v3-mcp-optimization
Activation
This is the description your AI agent reads to decide when to run this skill — the better it matches your request, the more reliably it fires.
MCP server optimization and transport layer enhancement for claude-flow v3. Implements connection pooling, load balancing, tool registry optimization, and performance monitoring for sub-100ms response times.Key capabilities
- →Implement connection pooling for MCP transports
- →Optimize tool registry lookups using hash tables
- →Apply load balancing for concurrent requests
- →Reduce cold-start latency
- →Monitor response times and memory usage
How it works
It refactors the transport and registry layers by introducing connection reuse and O(1) hash map lookups to remove linear search bottlenecks.
Inputs & outputs
When to use v3-mcp-optimization
- →Reducing MCP startup time
- →Optimizing tool registry lookups
- →Implementing connection pooling
About this skill
V3 MCP Optimization
What This Skill Does
Optimizes claude-flow v3 MCP (Model Context Protocol) server implementation with advanced transport layer optimizations, connection pooling, load balancing, and comprehensive performance monitoring to achieve sub-100ms response times.
Quick Start
# Initialize MCP optimization analysis
Task("MCP architecture", "Analyze current MCP server performance and bottlenecks", "mcp-specialist")
# Optimization implementation (parallel)
Task("Connection pooling", "Implement MCP connection pooling and reuse", "mcp-specialist")
Task("Load balancing", "Add dynamic load balancing for MCP tools", "mcp-specialist")
Task("Transport optimization", "Optimize transport layer performance", "mcp-specialist")
MCP Performance Architecture
Current State Analysis
Current MCP Issues:
├── Cold Start Latency: ~1.8s MCP server init
├── Connection Overhead: New connection per request
├── Tool Registry: Linear search O(n) for 213+ tools
├── Transport Layer: No connection reuse
└── Memory Usage: No cleanup of idle connections
Target Performance:
├── Startup Time: <400ms (4.5x improvement)
├── Tool Lookup: <5ms (O(1) hash table)
├── Connection Reuse: 90%+ connection pool hits
├── Response Time: <100ms p95
└── Memory Efficiency: 50% reduction
MCP Server Architecture
// src$core$mcp$mcp-server.ts
import { Server } from '@modelcontextprotocol$sdk$server$index.js';
import { StdioServerTransport } from '@modelcontextprotocol$sdk$server$stdio.js';
interface OptimizedMCPConfig {
// Connection pooling
maxConnections: number;
idleTimeoutMs: number;
connectionReuseEnabled: boolean;
// Tool registry
toolCacheEnabled: boolean;
toolIndexType: 'hash' | 'trie';
// Performance
requestTimeoutMs: number;
batchingEnabled: boolean;
compressionEnabled: boolean;
// Monitoring
metricsEnabled: boolean;
healthCheckIntervalMs: number;
}
export class OptimizedMCPServer {
private server: Server;
private connectionPool: ConnectionPool;
private toolRegistry: FastToolRegistry;
private loadBalancer: MCPLoadBalancer;
private metrics: MCPMetrics;
constructor(config: OptimizedMCPConfig) {
this.server = new Server({
name: 'claude-flow-v3',
version: '3.0.0'
}, {
capabilities: {
tools: { listChanged: true },
resources: { subscribe: true, listChanged: true },
prompts: { listChanged: true }
}
});
this.connectionPool = new ConnectionPool(config);
this.toolRegistry = new FastToolRegistry(config.toolIndexType);
this.loadBalancer = new MCPLoadBalancer();
this.metrics = new MCPMetrics(config.metricsEnabled);
}
async start(): Promise<void> {
// Pre-warm connection pool
await this.connectionPool.preWarm();
// Pre-build tool index
await this.toolRegistry.buildIndex();
// Setup request handlers with optimizations
this.setupOptimizedHandlers();
// Start health monitoring
this.startHealthMonitoring();
// Start server
const transport = new StdioServerTransport();
await this.server.connect(transport);
this.metrics.recordStartup();
}
}
Connection Pool Implementation
Advanced Connection Pooling
// src$core$mcp$connection-pool.ts
interface PooledConnection {
id: string;
connection: MCPConnection;
lastUsed: number;
usageCount: number;
isHealthy: boolean;
}
export class ConnectionPool {
private pool: Map<string, PooledConnection> = new Map();
private readonly config: ConnectionPoolConfig;
private healthChecker: HealthChecker;
constructor(config: ConnectionPoolConfig) {
this.config = {
maxConnections: 50,
minConnections: 5,
idleTimeoutMs: 300000, // 5 minutes
maxUsageCount: 1000,
healthCheckIntervalMs: 30000,
...config
};
this.healthChecker = new HealthChecker(this.config.healthCheckIntervalMs);
}
async getConnection(endpoint: string): Promise<MCPConnection> {
const start = performance.now();
// Try to get from pool first
const pooled = this.findAvailableConnection(endpoint);
if (pooled) {
pooled.lastUsed = Date.now();
pooled.usageCount++;
this.recordMetric('pool_hit', performance.now() - start);
return pooled.connection;
}
// Check pool capacity
if (this.pool.size >= this.config.maxConnections) {
await this.evictLeastUsedConnection();
}
// Create new connection
const connection = await this.createConnection(endpoint);
const pooledConn: PooledConnection = {
id: this.generateConnectionId(),
connection,
lastUsed: Date.now(),
usageCount: 1,
isHealthy: true
};
this.pool.set(pooledConn.id, pooledConn);
this.recordMetric('pool_miss', performance.now() - start);
return connection;
}
async releaseConnection(connection: MCPConnection): Promise<void> {
// Mark connection as available for reuse
const pooled = this.findConnectionById(connection.id);
if (pooled) {
// Check if connection should be retired
if (pooled.usageCount >= this.config.maxUsageCount) {
await this.removeConnection(pooled.id);
}
}
}
async preWarm(): Promise<void> {
const connections: Promise<MCPConnection>[] = [];
for (let i = 0; i < this.config.minConnections; i++) {
connections.push(this.createConnection('default'));
}
await Promise.all(connections);
}
private async evictLeastUsedConnection(): Promise<void> {
let oldestConn: PooledConnection | null = null;
let oldestTime = Date.now();
for (const conn of this.pool.values()) {
if (conn.lastUsed < oldestTime) {
oldestTime = conn.lastUsed;
oldestConn = conn;
}
}
if (oldestConn) {
await this.removeConnection(oldestConn.id);
}
}
private findAvailableConnection(endpoint: string): PooledConnection | null {
for (const conn of this.pool.values()) {
if (conn.isHealthy &&
conn.connection.endpoint === endpoint &&
Date.now() - conn.lastUsed < this.config.idleTimeoutMs) {
return conn;
}
}
return null;
}
}
Fast Tool Registry
O(1) Tool Lookup Implementation
// src$core$mcp$fast-tool-registry.ts
interface ToolIndexEntry {
name: string;
handler: ToolHandler;
metadata: ToolMetadata;
usageCount: number;
avgLatencyMs: number;
}
export class FastToolRegistry {
private toolIndex: Map<string, ToolIndexEntry> = new Map();
private categoryIndex: Map<string, string[]> = new Map();
private fuzzyMatcher: FuzzyMatcher;
private cache: LRUCache<string, ToolIndexEntry>;
constructor(indexType: 'hash' | 'trie' = 'hash') {
this.fuzzyMatcher = new FuzzyMatcher();
this.cache = new LRUCache<string, ToolIndexEntry>(1000); // Cache 1000 most used tools
}
async buildIndex(): Promise<void> {
const start = performance.now();
// Load all available tools
const tools = await this.loadAllTools();
// Build hash index for O(1) lookup
for (const tool of tools) {
const entry: ToolIndexEntry = {
name: tool.name,
handler: tool.handler,
metadata: tool.metadata,
usageCount: 0,
avgLatencyMs: 0
};
this.toolIndex.set(tool.name, entry);
// Build category index
const category = tool.metadata.category || 'general';
if (!this.categoryIndex.has(category)) {
this.categoryIndex.set(category, []);
}
this.categoryIndex.get(category)!.push(tool.name);
}
// Build fuzzy search index
await this.fuzzyMatcher.buildIndex(tools.map(t => t.name));
console.log(`Tool index built in ${(performance.now() - start).toFixed(2)}ms for ${tools.length} tools`);
}
findTool(name: string): ToolIndexEntry | null {
// Try cache first
const cached = this.cache.get(name);
if (cached) return cached;
// Try exact match
const exact = this.toolIndex.get(name);
if (exact) {
this.cache.set(name, exact);
return exact;
}
// Try fuzzy match
const fuzzyMatches = this.fuzzyMatcher.search(name, 1);
if (fuzzyMatches.length > 0) {
const match = this.toolIndex.get(fuzzyMatches[0]);
if (match) {
this.cache.set(name, match);
return match;
}
}
return null;
}
findToolsByCategory(category: string): ToolIndexEntry[] {
const toolNames = this.categoryIndex.get(category) || [];
return toolNames
.map(name => this.toolIndex.get(name))
.filter(entry => entry !== undefined) as ToolIndexEntry[];
}
getMostUsedTools(limit: number = 10): ToolIndexEntry[] {
return Array.from(this.toolIndex.values())
.sort((a, b) => b.usageCount - a.usageCount)
.slice(0, limit);
}
recordToolUsage(toolName: string, latencyMs: number): void {
const entry = this.toolIndex.get(toolName);
if (entry) {
entry.usageCount++;
// Moving average for latency
entry.avgLatencyMs = (entry.avgLatencyMs + latencyMs) / 2;
}
}
}
Load Balancing & Request Distribution
Intelligent Load Balancer
// src$core$mcp$load-balancer.ts
interface ServerInstance {
id: string;
endpoint: string;
load: number;
responseTime: number;
isHealthy: boolean;
maxConnections: number;
currentConnections: number;
}
export class MCPLoadBalancer {
private servers: Map<string, ServerInstance> = new Map();
private routingStrategy: RoutingStrategy = 'least-connections';
addServer(server: ServerInstance): void {
this.servers.set(server.id, server);
}
selectServer(toolCategory?: string): ServerInstance | null {
const healthyServers = Array.from(this.servers.values())
.filter(server => server.isHealthy);
if (healthyServers.length === 0) return null;
switch (this.routingStrategy) {
case 'round-robin':
return this.roundRobinSel
---
*Content truncated.*
When not to use it
- →If the system does not use Model Context Protocol
- →For small-scale tools where latency is negligible
Prerequisites
Limitations
- →Requires deeper understanding of the MCP protocol
- →May conflict with simple/default server configurations
- →Performance gains depend on server traffic patterns
How it compares
It prioritizes low-latency transport layer engineering over standard SDK implementations.
Compared to similar skills
v3-mcp-optimization side by side with the closest alternatives in the catalog.
| Skill | Installs | Updated | Safety | Difficulty |
|---|---|---|---|---|
| v3-mcp-optimization (this skill) | 1 | 6mo | Review | Advanced |
| exa-performance-tuning | 3 | 26d | Review | Intermediate |
| perplexity-rate-limits | 0 | 26d | No flags | Intermediate |
| documenso-performance-tuning | 0 | 26d | Review | Intermediate |
Try saying
Example prompts that trigger this skill in your AI assistant.
More by ruvnet
View all by ruvnet →You might also like
exa-performance-tuning
jeremylongshore
Optimize Exa API performance with caching, batching, and connection pooling. Use when experiencing slow API responses, implementing caching strategies, or optimizing request throughput for Exa integrations. Trigger with phrases like "exa performance", "optimize exa", "exa latency", "exa caching", "exa slow", "exa batch".
perplexity-rate-limits
jeremylongshore
Implement Perplexity rate limiting, backoff, and idempotency patterns. Use when handling rate limit errors, implementing retry logic, or optimizing API request throughput for Perplexity. Trigger with phrases like "perplexity rate limit", "perplexity throttling", "perplexity 429", "perplexity retry", "perplexity backoff".
documenso-performance-tuning
jeremylongshore
Optimize Documenso integration performance with caching, batching, and efficient patterns. Use when improving response times, reducing API calls, or optimizing bulk document operations. Trigger with phrases like "documenso performance", "optimize documenso", "documenso caching", "documenso batch operations".
gamma-performance-tuning
jeremylongshore
Optimize Gamma API performance and reduce latency. Use when experiencing slow response times, optimizing throughput, or improving user experience with Gamma integrations. Trigger with phrases like "gamma performance", "gamma slow", "gamma latency", "gamma optimization", "gamma speed".
juicebox-prod-checklist
jeremylongshore
Execute Juicebox production deployment checklist. Use when preparing for production launch, validating deployment readiness, or performing pre-launch reviews. Trigger with phrases like "juicebox production", "deploy juicebox prod", "juicebox launch checklist", "juicebox go-live".
openevidence-performance-tuning
jeremylongshore
Optimize OpenEvidence clinical query performance and response times. Use when improving latency, optimizing query efficiency, or tuning caching for clinical AI applications. Trigger with phrases like "openevidence performance", "openevidence slow", "optimize openevidence", "openevidence latency", "speed up clinical queries".