Use your own AI assistant

Run CloutOps from the AI assistant your team already uses.

Connect Claude, Codex, ChatGPT, or an internal assistant to your campaign workspace. Ask it to find an audience, plan a campaign, check status, read a report, or prepare work for approval. People still control publishing and spend.

Use CloutOps without switching to another chat product.

MCP is the shared connection layer. Your preferred assistant gets a small set of outcome-based tools, while CloutOps keeps campaign data, permissions, and approvals in one place.

Codex

Connect and sign in

Add CloutOps in Settings under MCP servers, enter the remote MCP URL, restart if prompted, then select Authenticate.

[mcp_servers.cloutops]
url = "https://client.cloutos.com/api/mcp"

# Then authenticate in Settings → MCP servers
# or run: codex mcp login cloutops

Claude

Connect and sign in

Add CloutOps as a custom connector, enter the MCP URL, then sign in with your CloutOps account when Claude opens the authorization flow.

Claude → Customize → Connectors
Add custom connector

Remote MCP URL
https://client.cloutos.com/api/mcp

Authentication
Sign in with CloutOps

ChatGPT

Remote MCP or OpenAPI

Use the remote MCP connector when it is enabled for your workspace. The OpenAPI schema remains available for GPT actions and internal tooling.

Remote MCP
https://client.cloutos.com/api/mcp

OpenAPI fallback
https://client.cloutos.com/api/agent/openapi

Portable assistant instructions

Give any capable assistant the same CloutOps operating rules.

The skill explains the buyer language, tool order, metric-source rules, and hard approval limits. OAuth users sign in normally; service keys stay outside the skill and chat history.

Connect your assistant

Add one remote MCP endpoint to Claude, Codex, ChatGPT, or another compatible tool. Sign in with CloutOps or use a scoped service key.

Connection setup

Work in plain English

Ask for an audience search, campaign plan, campaign status, report, or invoice. The assistant calls structured CloutOps tools behind the scenes.

See available tools

Keep people in control

Assistants may prepare drafts and recommendations. Authorized people still approve creative, price, placements, reports, and invoices.

See the controls

Small, clear toolset

Ask for outcomes, not internal workflow objects.

Each tool returns structured campaign data, so assistants can plan, compare, summarize, and prepare work without scraping dashboards or inventing state.

get_brand_context
ask_brand_brain
capture_brand_context
get_joker_context
chat_with_joker
list_joker_templates
get_joker_status
get_joker_history
request_joker_creative
get_joker_mission_history
get_creative_generation_capabilities
quote_creative_generation
create_creative_mission
list_creative_missions
get_creative_mission
list_creative_generations
get_creative_generation
confirm_creative_generation
cancel_creative_generation
search_audience
plan_campaign
list_brands
create_brand
register_brand_asset_version
create_brand_kit_draft
publish_brand_kit_version
snapshot_campaign_brand
list_campaigns
create_campaign_draft
get_campaign
get_campaign_report
get_invoice
recommend_approval

Sign in once

End users connect with Clerk OAuth, so CloutOps applies their existing workspace and role. Technical integrations can use a scoped, organization-bound service key instead.

Approval gates

Agents can draft and prepare. Humans approve booked placements, final pricing, placement exceptions, client reports, and invoices.