Inspiration

The Model Context Protocol (MCP) ecosystem has incredible potential, but many existing MCP servers have unclear tool names and descriptions that make them hard to discover and use. We wanted to create a solution that could intelligently improve MCP server interfaces without breaking existing functionality.

What it does

MCP Improver is a proxy service that enhances existing MCP servers by: Smart Tool Renaming: Transforms cryptic tool names like hubspot-get-user-details into clear ones like hubspot-authenticate-user Enhanced Descriptions: Improves tool descriptions to be more descriptive and user-friendly Seamless Proxy: Acts as a transparent layer between clients and MCP servers, applying improvements in real-time Dual Transport Support: Automatically falls back from SSE to HTTP transport for maximum compatibility Analytics Tracking: Monitors usage patterns and access counts for improved servers

How we built it

Node.js + Express: Core server infrastructure with TypeScript for type safety Official MCP SDK: Used @modelcontextprotocol/sdk for proper protocol compliance Prisma + SQLite: Database layer for storing improvements and analytics Dual Transport: Implemented SSE and HTTP transport fallback for robust connections JSON-RPC: Full MCP protocol support (tools, resources, prompts, health checks) Smart Mapping: Bidirectional name mapping between improved and original tool names Challenges we ran into Protocol Complexity: Understanding the MCP protocol specification and implementing proper JSON-RPC handling Transport Fallback: Ensuring seamless failover between SSE and HTTP transports when connections fail Name Mapping: Maintaining bidirectional mapping between improved names (for users) and original names (for API calls) Schema Validation: Working with Zod schema conversion from JSON Schema while handling TypeScript type issues Connection Management: Properly handling persistent connections and graceful shutdowns Accomplishments that we're proud of Full MCP Compliance: Supports all standard MCP methods (tools, resources, prompts) Zero Breaking Changes: Existing MCP clients work seamlessly with improved servers Intelligent Fallback: Robust transport layer that tries SSE first, then HTTP Real-time Improvements: Changes are applied dynamically without server restarts Production Ready: Includes health checks, logging, CORS, and proper error handling

Built With

Share this project:

Updates