Celigo for AI agents

Celigo is an integration platform that connects business applications and automates data flows between them, without a team writing custom middleware. Connect it once through Arc0, and your agent, or Claude, ChatGPT and Cursor, can use it through one MCP endpoint, limited to what each user approved.

Connect Celigo See the 117 actions ↓

Developer toolsAPI keyMCP + RESTceligo.com

AUDIT LOG · CELIGOPOLICY: acme-support

09:41:07 · claude · u_8f2read

celigo.list_jobs

List Jobs✓ allowed · 212ms

09:41:08 · claude · u_8f2read

celigo.get_tag

Get Tag✓ allowed · 164ms

09:41:09 · claude · u_8f2write

celigo.create_tag

Create Tag✓ approved · approved by user

09:41:12 · claude · u_8f2destructive

celigo.delete_tag

Delete Tag✕ blocked · policy: deny

EVERY CELIGO CALL, ON THE RECORD

01 · USE CASES

What agents do in Celigo.

Check a flow's connections

Check which connections a flow depends on before troubleshooting a broken data sync.

Create a new integration flow

Create a new flow to move data between two connected applications on a schedule.

Confirm before deleting an integration

Confirm before deleting an integration, since every flow and connection tied to it goes too.

02 · ACTIONS

117 Celigo actions, graded by risk.

Every Celigo action is tagged read, write or destructive, so one policy covers the whole app and new actions inherit the right default.

read

Look things up. Allowed by default.

celigo.get_tag
Get Tag
celigo.get_flow
Get Flow by ID
celigo.get_tags
Get Tags
celigo.get_user
Get User Share
celigo.get_users
Get All Users
celigo.list_jobs
List Jobs
celigo.get_export
Get Export
celigo.get_import
Get Import
celigo.get_script
Get Script
celigo.list_flows
List Flows
celigo.get_i_client
Get iClient by ID
celigo.list_exports
List Exports
celigo.list_imports
List Imports
celigo.list_licenses
List Licenses
celigo.get_connection
Get Connection by ID
celigo.get_flow_audit
Get Flow Audit Logs

+ 43 MORE

write

Create and change things. Allow, or ask the user first.

celigo.create_tag
Create Tag
celigo.update_tag
Update Tag
celigo.create_flow
Create Flow
celigo.update_flow
Update Flow
celigo.update_user
Update User
celigo.create_export
Create Export
celigo.create_import
Create Import
celigo.create_script
Create Script
celigo.update_export
Update Export
celigo.update_import
Update Import
celigo.update_script
Update Script
celigo.create_i_client
Create iClient
celigo.update_i_client
Update iClient
celigo.create_connection
Create Connection
celigo.update_connection
Update Connection
celigo.create_integration
Create Integration

+ 28 MORE

destructive

Delete, cancel or archive. Ask first, or deny outright.

celigo.delete_tag
Delete Tag
celigo.delete_flow
Delete Flow
celigo.delete_user
Delete User
celigo.delete_export
Delete Export
celigo.delete_import
Delete Import
celigo.delete_script
Delete Script
celigo.delete_iclient
Delete iClient
celigo.delete_all_state
Delete All State
celigo.delete_connection
Delete Connection
celigo.delete_integration
Delete Integration
celigo.delete_state_value
Delete State Value
celigo.delete_resolved_errors
Delete Resolved Errors
celigo.delete_all_resource_state
Delete All Resource State
celigo.delete_resource_state_value
Delete Resource State Value

03 · HOW IT WORKS

Celigo in three steps.

01Your users connect CeligoThey add their Celigo api key on Arc0 Connect, under your brand. It goes straight into the vault.
02You set the rulesReads run, writes like “create Tag” can wait for the user, and “delete Tag” can be denied outright.
03Any agent can actYour agent calls Celigo through the Arc0 SDK or MCP, and so can Claude, ChatGPT and Cursor. Every call lands on the audit log.

POLICY.TS

await arc0.policies.set('celigo', {
  read: 'allow',
  write: 'ask',        // create_tag
  destructive: 'deny',  // delete_tag
})

# Claude Code: the same connection, one URL
$ claude mcp add --transport http arc0 \
    https://mcp.arc0.ai/u/u_8f2

04 · AUTH AND DATA

How Celigo connects.

Users add their Celigo api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.

The same Celigo connection serves your agent over MCP and your own backend over REST and the proxy, so a user connects once. How Arc0 handles credentials →

AUTH: API key
CREDENTIALS: Per-tenant encrypted vault
MODEL SEES: Results only, never credentials
AUDIT LOG: Every call, on every plan

05 · WORKS WITH

Use Celigo from any agent.

Claude

ChatGPT

Cursor

Codex

VS Code

OpenAI Agents SDK

Claude Agent SDK

Vercel AI SDK

Mastra

LangGraph

06 · RELATED

More developer tools apps.

Addressfinder17 actions

Addresszen2 actions

Alchemy36 actions

ALL DEVELOPER TOOLS APPS →

07 · FAQ

Celigo and Arc0, answered.

Q01

Can I use Celigo with Claude, ChatGPT or Cursor?

Yes. Connect Celigo to Arc0 once, then add your Arc0 MCP URL to Claude, ChatGPT, Cursor, Claude Code or any other remote-MCP client. Each assistant only gets the Celigo actions you allow.

Q02

How do users connect Celigo?

Users add their Celigo api key on Arc0 Connect. It is encrypted in the vault, never shown to the model, and each user can rotate or revoke it at any time.

Q03

Which Celigo actions can my agent take?

117 in total: 59 read, 44 write and 14 destructive, such as “create Tag”. Your policies decide which of them each agent may call.

Q04

Can I stop my agent from deleting things in Celigo?

Yes. Actions like “delete Tag” are graded destructive. Set destructive actions to deny, or to ask so the user approves each one, and blocked calls still show up on the audit log.

Q05

Can my own backend call Celigo too?

Yes. The same Celigo connection is available over REST and through the Arc0 proxy, so your product and your agent share one connection per user.

Get started

Plug Celigo into your agent.

Your users connect Celigo once, under your brand. Your agent gets 117 actions behind your policies, with every call on the record.

Connect Celigo Browse all apps →

Free to build · MCP + REST · Audit log on every plan