Ultimate MCP Server

Production-ready MCP (Model Context Protocol) server deployed as Vercel serverless functions.

Live link : https://ultimate-mcp-server.vercel.app/

Organization Support

• We can help your organization design and build a custom MCP server at low cost.

• We also provide free support in architecture and decision-making for MCP adoption and rollout.

Executive Summary

• Purpose: expose a single MCP endpoint with a broad utility toolset for text, data, web, date/time, business, developer, and AI template workflows.

• Runtime model: stateless HTTP JSON-RPC over POST /mcp.

• Current scope: 90 tools across 7 categories.

• Platform: Vercel serverless functions (api/*.js).

Core Capabilities

• MCP JSON-RPC endpoint with initialize, tools/list, and tools/call support.

• Tool catalog endpoint for discovery (GET /tools).

• Health endpoint for monitoring (GET /health).

• Landing page endpoint (GET /).

System Flow

1. MCP client sends JSON-RPC request to POST /mcp.

2. api/mcp.js validates method and request body.

3. Request router dispatches by method:

• initialize returns protocol/server capability metadata.

• tools/list returns tool metadata and JSON schemas.

• tools/call resolves tool by name and executes its handler.

4. Tool result is serialized into MCP response content.

5. Errors are returned as JSON-RPC error objects.

Design Diagram (HLD)

flowchart LR
  A[MCP Client\nClaude/Cursor/Custom] -->|POST /mcp JSON-RPC| B[Vercel Route: /mcp]
  B --> C[api/mcp.js\nMCP Handler]
  C --> D[Tool Registry\nIn-memory object]
  D --> E[Tool Handler Execution]
  E --> C
  C --> A

  F[Health Probe] -->|GET /health| G[api/health.js]
  H[Catalog Consumer] -->|GET /tools| I[api/tools.js]
  J[Browser/User] -->|GET /| K[api/index.js]

SSD (System Sequence Diagram)

sequenceDiagram
  autonumber
  participant C as MCP Client
  participant M as /mcp (api/mcp.js)
  participant R as Tool Registry
  participant T as Tool Handler

  C->>M: POST tools/call {name, arguments}
  M->>R: Lookup tool by name
  alt tool exists
    R-->>M: Tool definition
    M->>T: Execute handler(arguments)
    T-->>M: Result object
    M-->>C: JSON-RPC success response
  else tool missing
    M-->>C: JSON-RPC error -32601
  end

LLD (Low-Level Design)

Components

• api/mcp.js: request parsing, CORS/method guards, JSON-RPC dispatch, tool execution, error mapping.

• api/tools.js: public catalog API grouped by category.

• api/health.js: health metadata for uptime checks.

• api/index.js: human-readable landing page.

• vercel.json: route mapping from public paths to serverless files.

JSON-RPC Contract (POST /mcp)

• initialize

• tools/list

• tools/call

Error Behavior

• 405 for non-POST methods on /mcp.

• 400 with JSON-RPC parse error for invalid payload.

• JSON-RPC -32601 for unknown method/tool.

• JSON-RPC -32000 for runtime handler failures.

State and Concurrency

• Server is stateless per request.

• Tool registry is in-process constant data.

• No persistent storage dependencies.

DDD (Domain-Driven Design View)

Bounded Context

• MCP Tool Execution Context: receives protocol requests, resolves tools, returns deterministic results.

Domain Concepts

• Entity: ToolDefinition (name, category, description, inputSchema, handler).

• Value Object: JsonRpcRequest (id, method, params).

• Value Object: JsonRpcResponse (result or error).

• Aggregate: ToolRegistry (consistency boundary for all tool definitions).

Domain Invariants

• Tool name must uniquely identify exactly one handler.

• tools/list must expose schema and description for callable tools.

• tools/call response must be serialized as MCP content text payload.

API Reference

Repository Structure

ultimate-mcp-server/
  api/
    index.js
    health.js
    tools.js
    mcp.js
  lib/
  tools/
  vercel.json
  package.json
  README.md

Local Development

npm install
npm run dev

Default local URL with Vercel dev:

• http://localhost:3000/mcp

• http://localhost:3000/tools

• http://localhost:3000/health

Deploy to Vercel

git clone <repo-url>
cd ultimate-mcp-server
vercel deploy --prod

MCP Client Integration

Claude Desktop

{
  "mcpServers": {
    "ultimate-mcp": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://YOUR-DEPLOYMENT.vercel.app/mcp"]
    }
  }
}

Generic MCP HTTP Example

curl -X POST https://YOUR-DEPLOYMENT.vercel.app/mcp \
  -H "Content-Type: application/json" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Tool Categories

• Text & Content

• Data & Math

• Web & Research

• Date & Time

• Business & Finance

• Developer Tools

• AI Prompts & Templates

Operational Notes

• CORS is enabled with Access-Control-Allow-Origin: *.

• /mcp handles OPTIONS for preflight requests.

• Project currently has no dedicated unit/integration test suite.

License

Contact: pratdala@gmail.com