When the external AI client connects to the content system interface, what background actions need to be confirmed first.
When an external AI client connects to the interface of the content system, it is necessary to confirm actions that will change the site status or affect operations beyond a single article: writing or modifying documents, batch import, backup and recovery, version upgrade, and switching at the multi-site level.AnQiCMS integrated MCP Server, the tool interface is based on intent directory unified convergence, supports Bearer Token authentication and round-level operation approval (write operation merging confirmation), and can be accessed by external AI clients such as Claude, Cursor.The focus of this design is not 'can it connect', but 'who decides after it connects'.
Three things to be determined before connection
The first is the authentication method. The access credentials determine who can access the backend through this interface. When using Bearer Token for authentication, the scope of the token and the rotation rhythm should be determined: the token given to external clients should not be equivalent to administrative privileges, and there should be a recyclable mechanism.The second is the exposure range. AnQiCMS's MCP interface sets the exposure range according to the intent domain, high-risk domains are closed by default, and need to be explicitly opened;Before connecting, you should first confirm which domains are needed for this session, and the rest should remain closed. The third item is the approval granularity. Read operations and write operations should be treated separately, with write operations merged and confirmed in rounds to avoid a series of unverified changes falling in one conversation.
Which background actions need to be confirmed first
It can be judged according to the radius of influence. The operation of writing single articles is easy to discover and correct when there is an error; the operation that affects the entire site status has a high cost when there is an error and may not be reversible.
The typical actions requiring confirmation include: creating or modifying documents and publishing directly, batch importing or overwriting existing documents, adjusting category and tag structures, template changes (affecting all pages simultaneously), backup and restore operations, version upgrades, multi-site switching and global settings changes. The three most significant actions are recovery, upgrade, and multi-site operations, as they do not affect individual data items.
AnQiCMS puts these three types in the default closed domains precisely to ensure that 'a single call from an external client' cannot be directly equated to 'being effective online'. Write operations are merged and confirmed at the round level, with one additional benefit: multiple writes in a single round are grouped on the same confirmation interface, and what people see is a complete set of changes rather than scattered prompts, providing a more thorough basis for judgment.
Why do write operations need to be merged and confirmed
Item-by-item confirmation sounds stricter, but the actual effect is often worse. When a task requires writing a dozen or more items in a row, item-by-item pop-ups turn confirmation into mechanical clicks, and people no longer read the content. After merging to the round level, the confirmation object changes from 'this item' to 'this batch', the site manager can check the scope and quantity by list, and can also decide whether to continue in one judgment.
This is a logic like code review: one readable set of changes, safer than ten isolated confirmations.
How to control batch entries like import interfaces?
Batch import is the easiest place for external clients to cross boundaries. AnQiCMS provides a document content import interface /api/import/archive, which supports querying whether a document exists by title and is used for batch import scenarios. When accessing this entry, it is recommended to do so:
- Search before write: Use title search to determine whether a document with the same name exists before import, decide whether to update or create a new one, and avoid repetition of the same topic;
- Limit the scope: Converge the import list within clear categories and file sets, where one task corresponds to a file that can be verified;
- Leave a rollback point: Make a backup before batch writing, AnQiCMS's backup covers data and static files, no need to supplement attachments separately when restoring;
- Post-event sampling: After import is complete, check a few items by category to confirm that the fields and status meet expectations.
Common questions
What can an external client do after obtaining a token?
It depends on the intended domain authorized by the token. By default, full-site domains such as backup, upgrade, and multi-site are turned off, and clients cannot trigger them directly; to expand capabilities, it must be explicitly enabled by the site owner.
How to verify whether the approval is really effective when connected?
Perform a write operation that is '明知会被拦截' for verification: initiate a modification class call, observe whether it enters the confirmation phase instead of directly committing to the database. Test read and write operations separately, and confirm that the boundaries meet expectations.
Are the interface capabilities consistent with the backend capabilities?
They are not entirely consistent. The interface side converges according to the intent directory, exposing a curated set of tools; the backend still has complete operations, which does not mean that the same action set can be accessed from the interface side.