MCP Server Demo
### CORRER APP
#### Instalar dependencias
```sh
uv sync
```
#### Correr APP
```sh
uv run server.py
```
### DOCKER
```sh
docker build -t mcp-server-demo .
```
```sh
docker run -p 8000:8000 --name app-mcp-server mcp-server-demo
```
### ADICIONAL
#### Instalar librerias
```sh
pip install "any"
```
#### Instalar en claude desktop
```sh
uv run mcp install server.py
```
#### Correr MCP inspector
```sh
uv run mcp install server.py
```
<img src="image.png">
#### CONEXION:
> Ejecutando el Script
```json
{
"mcpServers": {
"mcp-server-demo": {
"command": "C:\\Users\\my-user\\.local\\bin\\uv.EXE",
"args": [
"run",
"--with",
"mcp[cli]",
"mcp",
"run",
"C:\\Users\\my-path\\mcp-server-demo\\server.py"
]
}
}
}
```
> Ejecutando el servidor
```json
{
"mcpServers": {
"mcp-server-docker": {
"url": "http://0.0.0.0:8000/mcp/"
}
}
}
```
### REFERENCIAS
- [Python SDK for MCP](https://github.com/modelcontextprotocol/python-sdk?tab=readme-ov-file#installation) - SDK oficial de Python para Model Context Protocol
TDQS
Scored across 2 tools
The two tools have completely distinct purposes: one handles currency exchange rates, while the other performs basic arithmetic. There is no overlap or ambiguity between them.
The tools use different naming patterns: 'get_exchange_rate' follows a verb_noun convention, while 'sum' is a simple verb. This mixed approach is readable but inconsistent.
With only two tools, the server feels thin and poorly scoped. The tools (currency exchange and arithmetic) are unrelated, suggesting a lack of cohesive domain coverage.
For currency exchange, having only a 'get' operation without create/update/delete is a notable gap. For arithmetic, a single 'sum' tool lacks other basic operations like subtract or multiply, making the surface incomplete.