Build with an AI assistant

Updated 2026-08-13

The slow part of a wiki is rarely the clicking. It is having two hundred entries to get in, each needing the same six blocks. An AI assistant that speaks MCP can be pointed at your wiki and do that part, using your own subscription.

This is the same mechanism behind auto-translating, used for building rather than translating.

Give it a key of its own

A key of its own per assistant, each with its own role, each revocable without touching your account. The plaintext is shown once.

An assistant does not log in as you. It uses a service token: a key you issue, carrying its own role, revocable without touching your account.

Open Manage › Tokens. You need to be an admin.
Create one, name it something you will recognise later, and pick its role.
Copy the key. It is shown once, so if you lose it you issue a new one.
Put it in your assistant’s configuration.

Pick the lowest role that does the job. An assistant writing pages needs editor, not admin, and an admin token can change your settings and your shared layouts.

Issue several, one per assistant or task. The list shows when each was last used, so a token you do not recognise is a token to revoke.

What it can do

Everything goes through the same interface the editor uses. The assistant is not writing to your database, it is doing what a person with that role could do.

It canCreate and edit pages, add tables and rows, build layouts, set up navigation.

It cannotExceed its role, reach another wiki, or skip review.

It will notDelete, unless explicitly switched on. A misunderstanding should cost you a rollback, not a restore.

The order that works

The mistake is asking for a finished wiki in one go. Split it by what each side is good at.

You decide the shapeBuild ONE page properly, by hand, bound to a row and promoted to a shared layout.

It does the volumeGetting the data in, generating a page per row, filling in writing that follows a pattern.

You check a sampleThe first, one from the middle, and the sparsest you can find. Not all two hundred.

Because the shared layout is one template, a mistake in the design is one fix rather than two hundred. That is what makes handing the volume over safe.

Staying in control

Every change is a versionAnything an assistant does rolls back exactly like a person’s edit, and the history says what changed.

Turn review on while learningIts edits queue up for you instead of going live, which is a calmer way to find out what it does well.

Revoke when doneA token for a one-off import has no reason to keep working afterwards.