Skip to main content
Glama
felipecararo

US Weather MCP Server

by felipecararo
README.md
# MCP de Clima do Tempo para os EUA 🌤️

Servidor MCP (Model Context Protocol) que fornece informações sobre o clima dos Estados Unidos.

## 📋 Pré-requisitos

- Node.js (versĂŁo 14 ou superior)
- npm (gerenciador de pacotes do Node.js)

## 🚀 Instalação

1. Clone o repositĂłrio:
```bash
git clone https://github.com/FelipeCararo/mcp-intro.git
cd mcp-intro
```

2. Instale as dependĂŞncias:
```bash
npm install
```

## đź”§ Como Usar

### Compilar o projeto

Para compilar o cĂłdigo TypeScript:
```bash
npm run build
```

### Executar o servidor

ApĂłs compilar, execute o servidor MCP:
```bash
npm start
```

Ou execute diretamente o comando weather:
```bash
./build/index.js
```

### Script de inicialização

Você também pode usar o script shell incluído:
```bash
./start-mcp.sh
```

## 📦 Estrutura do Projeto

```
mcp-intro/
├── src/           # Código fonte TypeScript
├── build/         # Código compilado (gerado após build)
├── package.json   # Configurações e dependências
├── tsconfig.json  # Configurações do TypeScript
└── README.md      # Este arquivo
```

## 🛠️ Tecnologias Utilizadas

- **TypeScript** - Linguagem de programação
- **@modelcontextprotocol/sdk** - SDK do Model Context Protocol
- **Zod** - Validação de schemas e tipos

## 📝 Scripts Disponíveis

- `npm run build` - Compila o cĂłdigo TypeScript
- `npm start` - Executa o servidor compilado
- `npm test` - Executa os testes (ainda nĂŁo implementado)

## 🤝 Contribuindo

Sinta-se Ă  vontade para abrir issues e pull requests no repositĂłrio.

## 📄 Licença

ISC

## đź”— Links

- [RepositĂłrio no GitHub](https://github.com/FelipeCararo/mcp-intro)
- [Documentação do MCP](https://modelcontextprotocol.io)

TDQS

B3.1/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have clearly distinct purposes: one retrieves weather alerts for a state, while the other provides forecasts for a location. There is no overlap or ambiguity between these functions, making it easy for an agent to select the correct tool based on the user's request.

Naming Consistency5/5

Both tools follow a consistent verb_noun pattern with 'get_' as the prefix, ensuring predictability and readability. The naming style is uniform across the toolset, with no deviations or mixed conventions.

Tool Count2/5

With only two tools, the server feels thin for a weather domain, as it lacks essential operations like current conditions, historical data, or radar information. This minimal set may limit an agent's ability to handle comprehensive weather-related queries effectively.

Completeness2/5

The tool surface is significantly incomplete for a weather server, missing core functionalities such as current weather, radar maps, or severe weather details. While alerts and forecasts are useful, the absence of these key operations creates notable gaps that could lead to agent failures in broader scenarios.

Maintenance

ActivityInactive
ResponsivenessNo issues