The operational facts an agent needs when authoring wiki content through the MCP servers. The definitive tool registry is the live server (McpServerInitializer / KnowledgeMcpInitializer); verify counts there before editing docs that state them. As of 2.4.56 the admin server registers up to 29 tools and the knowledge server up to 21 (fewer when optional subsystems are not wired); MCP Integration has the full inventory.
/wikantik-admin-mcp) — authoring and analytics: write_pages, update_page, rename_page, rename_cluster, delete_pages, mark_page_verified, verify_pages, read_page, preview_structured_data, list_retrieval_queries, link/orphan/statistics tools, KG curation. Needs an mcp_admin (or all) key./knowledge-mcp) — read-only retrieval: assemble_bundle (the live retrieval gate), retrieve_context, read_pages, structural listing tools (list_clusters, list_pages_by_filter, list_tags, list_metadata_values), KG query tools, get_briefing. An mcp_read key is enough; it sees only publicly viewable pages.MCP_RATE_LIMIT_PER_CLIENT, global cap 500/s via MCP_RATE_LIMIT_GLOBAL). Modest parallelism is fine now; a genuinely tight loop still 429s (Retry-After: 1) — back off ~1s on 429. A bare-metal install uses its own template values and a build with no override defaults to 10 per client / 100 global (mcp.ratelimit.* in wikantik-mcp.properties).update_page requires expectedContentHash from read_page. On drift you get {updated:false, error:"hash mismatch", currentHash, currentVersion, latestContent} — rebase and retry without a new read. Other writers (a concurrent save, rename_page with updateLinks=true rewriting referrers, rename_cluster rewriting cluster: frontmatter) can move the hash between your read and write; this is normal.update_page metadata merges onto existing frontmatter — a one-field edit never wipes the rest; use removeKeys to delete a field; content (body) replaces wholesale and may be omitted for metadata-only edits.write_pages fails pages that already exist — use update_page for those; per-page results let you retry only failures.wikantik-wikipages (Main, the help pages, RecentChanges and similar). Only About stays editable through update_page by default (wikantik.systemPages.mcpEditable); delete and rename are refused for every system page. Main.md is generated from Main.pins.yaml and CI reverts hand-edits.type: runbook requires a structured runbook: block (when_to_use at least one entry, steps at least two, pitfalls at least one) or validation rejects the page./admin/apikeys), not config files.Discover (list_*, search) → write (write_pages/update_page) → lint (verify_pages with retrieval_readiness+seo_readiness) → live-check (assemble_bundle) → optionally ping_search_engines (IndexNow; Google needs manual GSC).