Skip to main content
Glama
yvanfreitas

MCP Test Server

by yvanfreitas
README.md
# MCP Test Server

Este projeto contém dois tipos de servidores:

1. **HTTP Server** (`server.js`) - Um servidor REST API tradicional
2. **MCP Server** (`mcp-server.js`) - Um servidor Model Context Protocol real

## ⚠️ Diferença Importante

### HTTP Server (`server.js`)
- ✅ Servidor REST API tradicional
- ✅ Funciona no navegador (http://localhost:3000)
- ❌ **NÃO compatível com Warp MCP**
- Uso: Testes manuais e desenvolvimento

### MCP Server (`mcp-server.js`)
- ✅ **Servidor MCP real compatível com Warp**
- ✅ Implementa protocolo JSON-RPC via stdio
- ✅ Expõe ferramentas (tools) para LLMs
- ❌ Não funciona no navegador
- Uso: Integração com Warp e outros clientes MCP

## Instalação

```bash
npm install
```

## Uso

### Para HTTP Server (desenvolvimento/testes)
```bash
npm start
# Acesse: http://localhost:3000
```

### Para MCP Server (Warp)
```bash
npm run mcp
```

### Testando HTTP Server
```bash
npm test
```

## Configuração do Warp

O arquivo `warp-mcp-config.json` está configurado para usar o **MCP Server real**:

```json
{
  "mcpServers": {
    "mcp-test-server": {
      "command": "node",
      "args": ["mcp-server.js"],
      "working_directory": "C:\\Users\\yvanf\\Documents\\MCP-test"
    }
  }
}
```

## Ferramentas Disponíveis no MCP

- `get_users` - Listar usuários
- `get_user` - Obter usuário por ID
- `create_user` - Criar novo usuário
- `get_tasks` - Listar tarefas
- `create_task` - Criar nova tarefa
- `search` - Buscar usuários e tarefas

## License

ISC

TDQS

B3.3/5.0

Scored across 8 tools

Disambiguation5/5

Every tool has a clearly distinct purpose with no ambiguity. The tools are cleanly separated by resource (task vs. user) and action (create, get, update, search), making it easy for an agent to select the correct one. There is no overlap in functionality that would cause confusion.

Naming Consistency5/5

The tool names follow a highly consistent verb_noun pattern throughout (e.g., create_task, get_user, update_task). All tools use snake_case and consistent verb choices (create, get, update, search), with no deviations or mixed conventions.

Tool Count5/5

With 8 tools, the count is well-scoped and appropriate for the server's purpose of managing tasks and users. Each tool earns its place, covering core operations without being overly sparse or bloated, fitting typical expectations for such a domain.

Completeness4/5

The tool set provides strong CRUD coverage for tasks (create, get, update, and implicit delete via absence) and users (create, get), with a search tool for both. A minor gap exists in not having update_user or delete operations explicitly, but agents can work around this with the available tools.

Maintenance

ActivityInactive
ResponsivenessNo issues