Three tasks, before / after
Content takeover during a migration
Before
Days of typing to bring over the client's existing content.
With the connector
Site tree and content recreated in series from the client's sources, images included.
create_rubriquecreate_articleadd_document_from_data
Traceable editorial maintenance
Before
The shared “admin” account on every site of the fleet.
With the connector
Everyone acts under their own identity and rights; a departure = a key revoked, immediately.
whoamiset_article_author
Deliver “AI-ready” sites
Before
Your clients' SEO stops at Google.
With the connector
JSON-LD FAQs + premium plugins (llms.txt, sitemap, robots): AI citability becomes a selling point for your clients.
set_faq
The tools mentioned are real — all 36 operations are documented.
Recommended plan for you
Solo — €49 excl. tax/month
Equip a first client site at €49/month; move to Edition (up to 10 sites + dedicated developments) to manage your whole fleet.
+ setup €490 excl. tax, one time only.
Your questions
One invoice per site?
Each site keeps its own dedicated, isolated server. Solo and Studio: one subscription per site. Edition bundles up to 10 sites in a single subscription; beyond that, ask for a group quote.
Can it be white-labelled?
That's an agency-offer conversation — see kimoun.com/serveur-mcp/ or request a quote, let's talk.
What happens when a collaborator leaves?
You revoke their API key in the relevant SPIP: immediate cut-off, without touching the other accounts.