Cloudivo MCP
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., "@Cloudivo MCP show CTE integration status"
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.
Cloudivo MCP
Cloudivo MCP is the Model Context Protocol server that will act as the AI gateway for the Cloudivo ecosystem. It exposes MCP tools, resources, and prompts while delegating business behavior to downstream Cloudivo services.
Vision
The long-term goal is a production-ready MCP server that gives AI clients a consistent interface to Cloudivo capabilities without embedding business logic in the gateway itself.
MCP owns orchestration, registration, authentication, and protocol boundaries.
Services own business rules.
Clients own outbound API communication.
Related MCP server: AIPOLabs MCP Server
Architecture Overview
The application follows a strict layered flow:
Tool -> Service -> Client -> REST API
Bootstrap is intentionally small and modular:
src/index.tsorchestrates startup.src/server/createServer.tscreates the MCP server.src/server/toolRegistry.tsregisters tools.src/server/resourceRegistry.tsregisters resources.src/server/promptRegistry.tsregisters prompts.src/server/startServer.tsattaches transport and starts the process.
See docs/ARCHITECTURE.md for the detailed architecture reference.
Folder Structure
src/
clients/ External API clients
config/ Centralized runtime configuration
prompts/ MCP prompt definitions
resources/ MCP resource definitions
server/ Bootstrap and registry modules
services/ Business-facing orchestration without transport concerns
tools/ MCP tool registration modules
types/ Shared application types
utils/ Small cross-cutting helpers only
tests/ Unit and registry tests
docs/ Project documentationSee docs/PROJECT_STRUCTURE.md for folder responsibility guidance.
Development Workflow
Install dependencies with
npm install.Start local development with
npm run dev.Build the project with
npm run build.Run the test suite with
npm run test:run.Validate TypeScript without emitting files with
npm run typecheck.
When adding new MCP functionality, keep src/index.ts unchanged and register new surfaces through the appropriate registry module.
Build Instructions
Prerequisites:
Node.js 22 LTS
npm 10+
Commands:
npm install
npm run build
npm startThe build emits compiled output to dist/.
Testing
Vitest is used for unit and registry tests.
npm testruns Vitest in the default mode.npm run test:runruns the suite once.npm run typecheckvalidates types without generating build output.
See docs/TESTING.md for the test strategy and roadmap.
Documentation
Core project references:
docs/ARCHITECTURE.mddocs/adr/README.mddocs/PROJECT_STRUCTURE.mddocs/DEVELOPMENT_GUIDE.mddocs/CODING_STANDARDS.mddocs/TESTING.mddocs/ENGINEERING_PRINCIPLES.mddocs/DEFINITION_OF_DONE.mddocs/SECURITY.mddocs/OPERATIONS.mddocs/adr/
Roadmap
Near-term priorities:
Harden configuration, logging, and error handling.
Add service and client foundations for external Cloudivo systems.
Expand test coverage across registries, services, and future clients.
See docs/ROADMAP.md for the phased plan.
Future Integrations
CTE
MailAPI
Leinaflow
Future Cloudivo services
Each integration will follow the same layering rules and will be introduced through dedicated client and service modules.
The first reusable integration boundary is the CTE client in src/clients/cte/CteClient.ts.
Available Tools
2 toolssystem.healthSystem HealthA
Returns the current status of the Cloudivo MCP Server.
Inputs: no named parameters. Returns: status, service, version
ticket.createCreate TicketC
Creates a ticket in the Cloudivo Ticket Engine.
Inputs: title (required), source (required), product (required), category (required), +4 more. Returns: url, success, ticketId, ticketNumber
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 2 tools
The two tools are completely distinct: one checks server health, the other creates tickets. There is no overlap or ambiguity between them.
The naming pattern is inconsistent: 'system.health' uses a noun, while 'ticket.create' uses a verb. While both use dot notation, the verb/noun mismatch makes the naming style confusing.
With only 2 tools for a server that includes a ticket engine, the tool set feels too thin. A ticket engine typically needs more operations, and the server's purpose appears underestimated.
The tool surface is severely limited: only ticket creation is supported, with no listing, retrieval, or update/delete operations for tickets. The system.health tool is fine but doesn't contribute to a complete workflow.
Related MCP Connectors
Model Context Protocol server for the Apideck Unified API. Connect any MCP-compatible agent framework to 100+ accounting systems, HRIS platforms, file storage providers, and more through one integration. More information https://www.apideck.com/mcp-server
A Model Context Protocol server for Wix AI tools
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
An MCP server that provides an API to LLMs to manage their JumpCloud resources.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceThis server implements the Model Context Protocol to facilitate meaningful interaction and understanding development between humans and AI through structured tools and progressive interaction patterns.57-
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that provides access to ACI.dev functions (tools) through either direct app-specific tools or a unified interface with dynamic tool discovery and execution based on user intent.255MIT
- AlicenseNot gradedqualityDmaintenanceA server that implements the Model Context Protocol, providing a standardized way to connect AI models to different data sources and tools.12MIT

Apideck MCPofficial
AlicenseAqualityAmaintenanceModel Context Protocol server for the Apideck Unified API. Connect any MCP-compatible agent framework to 100+ accounting systems, HRIS platforms, file storage providers, and more through one integration. More information https://www.apideck.com/mcp-server4394 npm21MIT