Nimbus Copiloto MCP Server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Nimbus Copiloto MCP Server What's the SLA status of ticket #1234?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Nimbus Copiloto — Helpdesk MCP Server
MCP server for Helpdesk Nimbus, the support ticketing platform of Nimbus S.A.S. It lets an AI assistant operate the helpdesk: search cases, view history, escalate, respond, and measure SLA compliance.
This is a learning environment. Nimbus S.A.S. is a fictional company. The repository exists to learn FastMCP by building a project with the shape and demands of a real one.
Quick start
# 1. Dependencias
uv sync
# 2. Sembrar la base de datos
uv run python -m backend.seed
# 3. Levantar el backend de la empresa (terminal aparte, déjalo corriendo)
uv run uvicorn backend.main:app --reload --port 8000
# 4. Correr las pruebas
uv run pytest -vWith the backend running: http://127.0.0.1:8000/docs
Related MCP server: tickiti-mcp
The MCP server
# Correrlo
uv run python -m nimbus_mcp.server
# Inspeccionarlo en el navegador
uv run fastmcp dev src/nimbus_mcp/server.pyIt is also available inside Claude Code thanks to .mcp.json. Check with /mcp.
Structure
mcp-test/
├── backend/ # API interna de Nimbus — NO SE TOCA
│ ├── main.py # FastAPI: tickets, clientes, agentes, KB, métricas
│ ├── db.py # Esquema SQLite
│ └── seed.py # Generador de datos de prueba
├── src/nimbus_mcp/ # El servidor MCP — aquí trabajas
│ └── server.py
├── tests/ # Pruebas
├── data/nimbus.db # Base sembrada (regenerable)
└── docs/ # Documentación del proyectoDocumentation
Document | What it's for |
Start here. What MCP is, how to get everything running, learning path | |
The long plan: 8 phases to AI Engineer | |
The company, the team, why the project exists | |
The domain: tickets, statuses, SLA, glossary | |
API contract consumed by the MCP | |
Phase 1 — the MCP tickets | |
Phase 2 — the copilot tickets | |
Where the last session left off |
The plan
This repository is Phase 1 of eight. The system grows in layers: MCP → copilot → evals → RAG → guardrails → observability → own models → production. The complete map is in docs/RUTA_AI_ENGINEER.md.
Versions
Python 3.13 · FastMCP 3.4.7 · FastAPI 0.141 · pytest 9.1
Available Tools
3 toolsconsultar_ticketA
Consulta los datos de un ticket específico. Toca la red para obtener los datos. Únicamente lee información de un ticket, no modifica nada.
Casos de uso:
El agente pregunta por un ticket con su código.
Formato de código: TCK-0000 - Pudiendo ser los 0000 cualquier número. El código no distingue entre mayúsculas y minúsculas.
Inputs: codigo (required). Returns: object
listar_estados_de_ticketA
Lista los estados posibles de un ticket y su explicación. No toca la red, es una tool únicamente informativa, no devuelve los datos de un ticket específico sino de la lista de estados posibles y válidos que trabajamos en Nimbus.
Casos de uso:
El agente pregunta por los estados que existen para un ticket.
El agente no entiende por qué el estado de un ticket y necesitamos aclararlo.
El agente pide explicación de por qué no puede tocar un ticket.
Inputs: no named parameters. Returns: object
pingA
Verifica que el servidor MCP de Nimbus esta vivo.
Inputs: no named parameters. Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: ping checks server liveness, listar_estados_de_ticket provides reference information about ticket states, and consultar_ticket retrieves a specific ticket's data. There is no ambiguity or overlap between them.
Tool names follow a consistent verb_noun pattern (ping, listar_estados_de_ticket, consultar_ticket). Although 'ping' is a single verb, it is a standard convention and the other two follow the same style, ensuring predictability.
With 3 tools, the server is appropriately scoped for its narrow purpose of ticket status lookup and retrieval. Each tool is essential and there are no redundant or missing operations for the stated functionality.
The server covers the core read operations: checking health, listing possible ticket states, and fetching a specific ticket. A notable gap is the lack of a 'list_all_tickets' tool, but given the description, the server appears intentionally focused on individual ticket queries, so this is a minor omission rather than a critical failure.
Related MCP Connectors
AI-powered incident management and server monitoring via MCP.
MCP server for Support & Service Management
AI-native helpdesk hosted in Germany: tickets, replies, KPIs and knowledge base over MCP.
Remote MCP server for managing Muninx tickets, messages, ticket search, and support analytics.
Related MCP Servers
- AlicenseAqualityCmaintenanceAn MCP-compliant server that enables AI assistants like Claude Desktop to access and analyze Intercom support tickets with full conversation history.48Apache 2.0

tickiti-mcpofficial
AlicenseBqualityBmaintenanceAn MCP server that exposes the Tickiti helpdesk API to AI assistants, enabling ticket management and helpdesk operations via natural language.11MIT- FlicenseNot gradedqualityDmaintenanceMCP server for Nimbus Operations Copilot that enables AI agents to search help docs, customer data, invoices, and tickets, and propose refunds/tickets with human approval for writes.-
- FlicenseNot gradedqualityDmaintenanceMCP server that provides IT support tools to search known incidents, check ticket status, and create ticket drafts, enabling an AI assistant to help users with IT support queries.-