APIs and tools both execute logic in integrator.io, but they serve different purposes. Use this guide to decide which to build. It is recommended to build reusable logic as a tool and if external ...
To see the guardrails in your account, navigate to AI studio → Guardrails. Note If you haven’t added any guardrails yet, click Create guardrail to add one. The guardrails list view displays key ...
Input control defines how you pass data from a flow to a guardrail. Correct input setup ensures consistent evaluation per record: Pass the correct context for evaluation Combine structured re...
A guardrail returns structured JSON output for every record. This output is consistent across all policy types and cannot be modified. At minimum it includes the decision: flagged (true/false). De...
A model context protocol (MCP) server is a managed server in integrator.io that publishes selected integration capabilities as MCP tools. These MCP tools can be discovered and invoked by any MCP-...
Before you begin You must be an account owner or admin to create an MCP server or manage tools. You’ll need at least one API to expose it as a MCP tool. You must create an account alias bef...
To see all MCP servers in your account, navigate to AI Studio → MCP servers. The MCP server list view displays key information for each server in the respective fields: From Actions (…), you can:...
Celigo Identity is the unified identity and access management system for end users in Celigo. It controls who can use Celigo capabilities through external clients, today, MCP servers from Claude, C...
End user groups let you manage MCP server access for multiple end users at once. Instead of granting each end user access to each MCP server individually, create a group "Engineering" or "Operation...
End user authentication controls how end users sign in when connecting to MCP servers from AI clients such as Claude or Cursor. It is configured separately from the account's SSO, which applies to ...