Areca DocsAgency connector
One AI connector for every client and site you manage, production and development, with the site chosen on each call. Who can use it, how to find a site, what it can and cannot do, and how to connect, revoke and audit it.
The agency connector is one AI connector for every client and site that you, as an agency admin, can manage. Instead of adding a connector for each site, you add this one address to your AI app once. Each request names the site it acts on, and the answer says where the change happened.
It is for agency admins only. Owners and editors do not see it, and the address answers as if it did not exist for them.
Connect an AI app
The agency connector address is:
https://<your CMS>/api/agency/mcpOpen Agency › Connect AI. Under Your connector URL, select Copy connector URL. The page shows the same install steps as a site's Connect AI page: Claude, ChatGPT, Claude Code, Cursor, VS Code and other apps. The Install the Areca skills command on that page also accepts this address, and registers it as areca-agency. See agent skills.
You can sign in two ways:
- Connect an app (recommended). Your AI app opens a browser, you sign in to Areca, and you approve on the consent screen. The approval says plainly: "This app can read and change every client and site, including production, and go live." Agency admins confirm with a fresh authenticator code before Allow works.
- A personal agency key. Create it under Personal keys on Agency › Connect AI, with Create AI key. You choose how long it lasts: 30 days, 90 days, 1 year or never. Creating a key also needs a fresh authenticator code. The key is shown once. Send it as
Authorization: Bearer <key>. An agency key works only on the agency address, not on a site's connector.
Both need two-factor sign-in on your account. Without it, the address answers 403 with mfa_required.
Find the site
Every site tool takes a site argument: the site's slug, for example acme for production or acme-dev for its development environment. There is no "current site", so the conversation never depends on which site was used last.
Use the navigation tools to find the slug:
| Tool | What it does |
|---|---|
list_clients | Lists your clients with their slugs and how many sites each has. |
list_sites | Lists sites, production and development. Pass client to list one client. Each row has the slug, name, client, environment, the linked site (a development environment's production site, or a production site's development environment), the publishing mode, whether a live release exists, and how many approved entries wait for the next go live. |
find_site | Finds sites by text: the site name, slug, client name or production URL. Returns up to 50 matches. |
Every result from a site tool includes a site object (slug, name, client, environment), so you can see where each change was made.
What you can do
The agency connector offers every tool a site's connector offers, with the same names and rules, plus the three navigation tools. The tools for content, the library, schema, languages and publishing are described in MCP endpoint and tools. Agency admins have the rights of an agency admin on every site, so this includes:
- Create, read and change entries, sections and the library on any site.
- Mark entries ready, and change content types (collections) and site content sections.
- Go live, roll back, cancel a queued build, schedule entries and cancel schedules on production sites.
- Create a development environment for a production site, and reset, push and copy from a development environment (see Development environments).
Some tools only apply to one kind of site. The tool is still listed, and it refuses the call with a short reason when the site does not fit:
- On a development environment, go live, rollback, cancel build, the release and build status tools, and scheduling are refused. The refusal says to push to production first.
- On a production site, the push, reset and copy tools are refused. The refusal says to use the site's development environment slug from
list_sites.
Going live without an extra tick
Per-site connectors have an Allow going live tick, which is off by default. The agency connector does not: an agency admin's connection can go live on any production site without it. This is the one place where the agency connector is different from a site's connector, and it is why the consent screen says "and go live".
Going live still needs a reason. The AI app is told to name the client and the site, and to get your confirmation, before it changes a production site. Production changes reach visitors once the site goes live.
Production changes are not blocked
The agency connector writes to production sites with the same rights you have in the CMS. The assistant is told to confirm before a production change, and the push from a development environment is a review step. Neither is a lock. Use the list and the confirmation to keep control.
Credentials and revocation
- Keys and apps are yours. An agency key or an app you connected works only for you, and only while you are an agency admin with two-factor sign-in.
- Losing the role ends them. When someone stops being an agency admin, their agency keys and apps are revoked straight away. Deleting the account does the same. A blocked account is refused on every request until it is unblocked.
- Disconnect or revoke. Open Agency › Connect AI to see your Personal keys and Connected apps. Select Revoke on a key or Disconnect on an app to stop it. Revoking stops the key or app at once, in every place it is used.
- Site connections are separate. A connection to one site does not give access through the agency connector, and the agency connector does not change the site connections you have.
- Rate limit. Requests are limited to 120 a minute for each key or app, shared across all sites. Wait for
Retry-Afterwhen you see429.
Audit
Every change made through the agency connector is written to the audit log for the site it changed. The record names the agency connector as its source, and the name of the key or app that made the call. Changes to a development environment are visible to agency admins only.
When something does not work
401with "Sign in": the app needs to sign in again, or the key is wrong. Reconnect the app from Agency › Connect AI, or create a new key.403withmfa_required: turn on two-factor sign-in in your account settings.404"Site not found": either the address is wrong, or your account is not an agency admin. The same answer is given to anyone without access, so check the address first.- "No site with slug … is available to you": call
list_sitesorfind_siteand use the slug it returns. - Go live refused on a development environment: that is expected. Push to production first, then go live on the production site.
Related
- Connect AI for connecting a single site.
- Development environments for the review-and-push workflow.
- MCP endpoint and tools for every tool and its inputs.
- Tokens for how keys and connections are stored and revoked.
Development environments
Try content and code changes on a copy of a live client site, then push the reviewed changes to production. The agency workflow, the local token steps, the push screen, and how AI apps work on a development environment.
Languages
Publish a site in several languages. Set the main language, choose required languages, translate fields and URL paths, and see what happens when the main language changes or a language is removed.