# HEADLESS ACCESS

## The full power of Celigo, wherever your team works

The UI for those who want it. The terminal for developers. The LLM for AI-first teams. One platform, every surface.

## Your team doesn't work in one place. Your automation platform shouldn't either.

Access the full Celigo platform from the UI, terminal, or LLM without breaking your flow.

### Full platform access in the UI, Terminal, or your LLM

For Celigo builders

The full visual platform experience

Build, manage, and monitor integrations within Celigo's core platform interface — including Celigo Ora.

### For developers

Build and manage from your terminal or IDE

All the power of Celigo, wrapped in a clean native command-line interface. No browser, no context-switching.

### For AI-first teams and agents

Build and manage automations from your LLM

Build and manage automations directly from your LLM of choice. Celigo becomes the integration layer AI can act through.

## Built for the teams driving automation forward

### IT leaders and architects

Your developers live in the terminal. Build, run, and manage automations from the CLI with no security tradeoffs.

### AI-first teams

Celigo Platform MCP makes the platform natively accessible to AI agents. Build, manage, and trigger automations directly from your LLM of choice.

## Go deeper

Pick the surface that fits how your team builds — explore the developer CLI or the AI-native Platform MCP, or jump straight into the documentation.

### Celigo CLI
Build and manage Celigo integrations directly from your terminal or IDE.

### Celigo Platform MCP
Connect your LLM to the full power of Celigo's intelligent automation platform.

Prefer to start with the docs? [Read the documentation](https://developer.celigo.com/)

## See headless in action

Hear how Bring IT uses Celigo CLI and Platform MCP to build faster, empower AI, and deliver measurable ROI in real-world workflows.

## Frequently asked questions

### What does it mean that Celigo is headless?

[Headless](/content/blog/celigo-headless/index.html) means you can access the full Celigo platform without the browser UI. Developers use Celigo CLI from their terminal or IDE; AI-first teams and agents use Celigo Platform MCP from their LLM. All three surfaces — UI, CLI, Platform MCP — run on the same platform with the same capabilities.

### Does headless access mean I lose any platform features?

No. Headless access is additive — it doesn’t remove or limit anything. Existing integrations, connections, and configurations stay as they are. CLI and Platform MCP add ways to access the same full feature set.

### What is Celigo CLI?

A native command-line interface that wraps the Celigo REST API. Build, manage, and operate integrations from your terminal or IDE without a browser. Installs via npm; supports multiple account profiles, scripting, and CI/CD.

### What is Celigo Platform MCP?

A hosted server that lets AI agents operate your Celigo account in plain language using the Model Context Protocol. Connect any MCP-compatible client (Claude, ChatGPT, Cursor, VS Code), give it a Celigo API token, and it can read, build, run, and troubleshoot integrations through conversation.

### How is Celigo's headless access different from other iPaaS platforms?

Most iPaaS are browser-only. Celigo is the first to offer a full headless layer — both a developer-native CLI and an AI-native MCP server — with complete feature parity with the UI.

### What permissions do CLI and Platform MCP users have?

Both use the same Celigo API token-based permissions as the REST API. The agent or developer can only do what the token allows, scoped to their account and environment. IT and security teams keep full governance.

## See Celigo working the way your team works

Get a demo and we'll show you headless access in action — CLI, Platform MCP, or both.
