What problem does it solve?
This Skill helps you package Celigo Tool and builder-mode API capabilities into a Model Context Protocol (MCP) server so external AI agents can call your integrations as tools over a standardized endpoint.
Core Features & Use Cases
- MCP server endpoint design: Create a unique
relativeURI that identifies the MCP server path for clients.
- Tool vs API exposure: Expose Celigo Tools (as MCP tools with optional annotations and overrides) and expose builder-mode APIs (as MCP tools without annotations/overrides).
- Agent behavior hints: Configure MCP-standard annotations like
readOnlyHint, destructiveHint, idempotentHint, and openWorldHint for safer, better tool usage.
- Per-server customization: Use overrides (especially connection overrides) so the same underlying Tool can operate against different resources per server.
- Validation guidance: Ensure tool input schemas are MCP-compatible (tool input must be an object at the root) and enforce name uniqueness across all exposed entries.
Quick Start
Use the building-mcp-servers skill to plan the capabilities you want to expose, then define an MCP server with a valid relativeURI and add tools[] and/or apis[] entries that reference existing Celigo resources.