MCP Server
# MCP Server
A modern AI service proxy built with Cloudflare Workers and Hono framework, supporting multiple AI providers including Anthropic Claude and OpenAI.
<a href="https://glama.ai/mcp/servers/@quang-pham-dev/my-mcp-server">
<img width="380" height="200" src="https://glama.ai/mcp/servers/@quang-pham-dev/my-mcp-server/badge" alt="Server MCP server" />
</a>
## Features
- Multi-provider AI service integration (Anthropic Claude, OpenAI)
- Built on Cloudflare Workers for global edge deployment
- Fast and efficient request handling with Hono framework
- Type-safe implementation with TypeScript
- CORS support for cross-origin requests
- Health check and provider info endpoints
## Prerequisites
- Node.js (LTS version recommended)
- npm or pnpm package manager
- Cloudflare account for deployment
- API keys for supported AI providers
## Installation
1. Clone the repository
2. Install dependencies:
```bash
pnpm install
```
## Environment Setup
1. Copy the example environment file:
```bash
cp .env.example .env
```
2. Configure your environment variables in `.env` with your API keys and preferences
## Development
Start the development server:
```bash
pnpm run dev
```
The server will start in development mode with hot reloading enabled.
## Deployment
Deploy to Cloudflare Workers:
```bash
pnpm run deploy
```
## API Endpoints
### Health Check
- `GET /health`
- Returns server status and configuration
### Provider Info
- `GET /api/provider`
- Returns current AI provider and model configuration
### MCP API
- `POST /api/mcp`
- Main endpoint for AI service requests
- Accepts JSON payload with context, query, and options
## Project Structure
```
├── src/
│ ├── controllers/ # Request handlers
│ ├── models/ # Type definitions
│ ├── services/ # AI service implementations
│ └── index.ts # Main application entry
├── public/ # Static assets
└── wrangler.jsonc # Cloudflare Workers configuration
```
## License
MITTDQS
Scored across 5 tools
The tools have distinct names like api-client, data-processor, and file-handler, which suggest different purposes, but descriptions are generic (e.g., 'ApiClient tool description'), leaving some ambiguity about their specific functions. Without detailed descriptions, it's unclear if there's overlap in processing or handling tasks.
Naming is inconsistent with mixed conventions: hyphen-case (api-client, data-processor, my-tool), snake_case (example_tool), and camelCase (FileHandler). This lack of a predictable pattern makes the tool set harder to navigate and could confuse agents.
With 5 tools, the count is reasonable for a general-purpose MCP server, suggesting a moderate scope. It's not too thin or heavy, though the generic nature of the tools makes it hard to assess if this number fits a specific domain perfectly.
Given the generic tool names and descriptions, it's impossible to infer a clear domain, making completeness assessment difficult. However, the set lacks obvious CRUD or lifecycle coverage, and tools like 'example_tool' and 'my-tool' seem vague, indicating significant gaps for any specific workflow.