Help Center
Everything you need to understand and configure CONTROL: AI provider APIs, MCP connections, and CONTROL AI.
Choose your path
Three different things, often confused. CONTROL keeps them separate.
I want to use an AI model
Connect an AI Provider API (OpenAI, Anthropic, Google, Kimi) and use supported models directly inside CONTROL. Your provider, your billing.
Connect APIAlready have an account? Connect providers from Integrations.
I want to give AI access to tools
Connect MCP so a compatible AI client can use your approved CONTROL tools and data, with your authorization.
Connect MCPSee the step-by-step guide below.
I want CONTROL's native AI
CONTROL AI is CONTROL's own AI experience inside the AI workspace, included with an eligible CONTROL subscription.
View plansAccess is checked when you sign in.
How it works
The provider powers the model. CONTROL's policy layer governs every call. MCP connects tools and external data.
AI Provider
OpenAI · Anthropic · Google · Kimi
AI Model
The model that generates your response
CONTROL
Policy layer
MCP / Tools
Connected tools
External Data
The data your tools can reach
MCP vs AI Provider API vs CONTROL AI
They are three different things, and CONTROL treats them differently.
| AI Provider API | MCP | CONTROL AI | |
|---|---|---|---|
| What it is | The model that generates your responses | Connects tools and external data | CONTROL's own native AI experience |
| What you connect | Your provider API key | An MCP connection, authorized with OAuth | Your CONTROL subscription |
| What it gives you | Supported models inside CONTROL | Approved tools and data for AI clients | The built-in AI workspace |
How to connect MCP
MCP (Model Context Protocol) lets AI clients use tools and external data. CONTROL supports one direction today, and keeps the two directions clearly separate.
Use CONTROL from a compatible AI client
CONTROL exposes an MCP server. Your AI client connects to CONTROL, you authorize the connection with your CONTROL account, and the client can use the approved tools and data.
External AI client
Claude Desktop or another MCP-compatible client
CONTROL MCP server
The connection you add to your client
CONTROL authorization
You approve access with OAuth
Approved tools & data
Only what CONTROL is allowed to expose
- 1Create your CONTROL account and workspace.
- 2Open your compatible AI client, for example Claude Desktop or another MCP-compatible client.
- 3Add the CONTROL MCP server to your client using the MCP connection details provided with your CONTROL account.
- 4Complete the OAuth authorization and approve the requested access.
- 5Use the approved tools and data from your AI client.
Connect external MCP servers into the CONTROL AI workspace
Connecting external MCP servers as tools inside the CONTROL AI workspace is not available yet. When it ships, you will review the available tools, enable only the ones you want, and every call will pass through the same security chain described below.
MCP security
Every MCP call through CONTROL follows one chain:
authentication → authorization → policy → MCP permissions → execution → audit
The connection is authorized with your CONTROL account (OAuth). Organization policies and permissions are enforced server-side before anything runs, and every action is recorded in the audit log.
AI Provider APIs
Connect an API, choose a model, use it inside CONTROL. Keys are stored securely for your organization and never displayed in plain text after they are saved.
OpenAI
Create a key at platform.openai.com → API keys (starts with sk-).
Chat, vision and image generation.
Anthropic
Create a key at console.anthropic.com → API keys (starts with sk-ant-).
Chat and vision.
Create a key at aistudio.google.com → Get API key.
Chat and vision.
Kimi (Moonshot)
Create a key at platform.moonshot.ai → API keys (starts with sk-).
Chat with Kimi models.
DeepSeek
Create a key at platform.deepseek.com → API keys.
Unlocks the IA Control Pro model in the AI workspace.
Provider billing
Your model requests are billed by the connected AI provider according to their API pricing, on your provider account.
CONTROL subscription
Your CONTROL plan determines access to CONTROL features and CONTROL AI benefits. It does not add credit to an external provider account.
If your provider account reaches a usage or credit limit, the error comes from that provider. Upgrading a CONTROL plan never increases an external provider balance, and CONTROL never silently falls back to another provider.
Video help
Setup tutorials for MCP-compatible AI clients. These videos were made by third parties, not by CONTROL, and are provided as external tutorials.
Claude MCP setup
OpenAI MCP setup
