Criota for AI assistants
Criota, inside the assistant you already use.
Connect Claude, ChatGPT, Cursor or your own agent to your Criota account. Ask what is waiting on you, how a campaign is filling, what you have been paid. It answers from your account, not from a guess, and it changes nothing you have not said yes to.
Included on every plan. You pay your own AI provider; Criota does not charge for its use.
What it is like
Ask in your own words.
The owner of a venue or a venue group.
You ask
- “Which applications are waiting on me?”
- “How is each of my campaigns filling?”
- “Draft me a campaign for a quiet Tuesday.”
- “Approve the oldest application for Saturday.”
It can look up
Applications
Creators who applied to your campaigns: who, which campaign, and where each application is up to.
My campaigns
Your campaigns across venues, with how each is filling.
Drafts to review
Creator drafts waiting on your verdict.
Find creators
Creators filtered by fit, each with their levels. Levels only, never scores.
Draft a campaign
Describe a goal in a sentence; get a full campaign drafted. Nothing is published.
Answers are outcomes and levels: what was offered, what was paid, where a job is up to, how a creator has done. How Criota works those out stays in-house, for an assistant exactly as it does on the dashboard.
Yours to control
An assistant is a guest on your account.
You let it in, and out
You sign in from your assistant and agree to what it may do, or you create a key in your dashboard. Either way Criota keeps only a fingerprint it cannot read back. End the connection and the assistant stops at once.
It can do no more than you
Every request runs through the same checks as the dashboard. A venue's account is connected by its owner alone; staff and agencies cannot connect an assistant or create a key.
It asks before it changes anything
Applying, publishing, approving, answering a draft, licensing a post: before any of them you are shown what will happen, to whom and what it costs, and nothing happens unless you say yes. A connection made only to read can change nothing at all.
Every request is recorded
Which connection asked for what, and when. Never what was said back.
Connect in a minute
Three steps.
- 1
Give your assistant the address
The one below. An assistant that signs in needs nothing else; one that takes a key gets a key from your dashboard as well.
- 2
Say what it may do
It sends you to Criota. You sign in, see what it is asking for, choose whether it may make changes, and say yes.
- 3
Ask
In your own words. The assistant finds the right part of Criota itself.
The address
https://mcp.criota.com/mcpBy signing in
No key to copy. The assistant sends you to Criota, and you say yes there.
In Claude, open Settings, then Connectors, add a custom connector and give it this address.
https://mcp.criota.com/mcpIt sends you to Criota to sign in. You see what it is asking for, choose whether it may make changes, and say yes. No key to copy.
With a key
For an assistant that takes a key instead. Any assistant that speaks the Model Context Protocol over HTTP and can send a header will connect.
Run this in a terminal.
claude mcp add --transport http criota https://mcp.criota.com/mcp \
--header "Authorization: Bearer YOUR_CRIOTA_KEY"Start Claude Code and ask it about your Criota account.
Replace YOUR_CRIOTA_KEY with your key.