MCintelligentplus DocsMCwiki
Sync selected MCwiki spaces and pages into your knowledge base
MCwiki Integration Setup Guide
The MCwiki connector uses your MCwiki deployment's third-party content API to bring wiki content into MCintelligentplus. You pick which spaces to sync, and MCintelligentplus indexes their page trees into the workspace knowledge base — searchable in chat alongside your uploads, notes, and other connectors.
How it works
- Space scan — enter the MCwiki base URL and a bearer token, and MCintelligentplus calls the server's space API to list every space that token can access. Credentials used for a scan are used only for that request and are not stored until you connect.
- Selected spaces only — you choose exactly which spaces to import. Nothing else on the MCwiki server is read.
- Page trees and content — for each selected space, the connector walks the page tree and fetches every page's content through the third-party content API. HTML content is converted to Markdown; non-text macros (for example attachment-only pages) are kept as-is when Markdown cannot represent them.
- Folder structure — each MCwiki space becomes a folder in the workspace, and page hierarchy is mirrored beneath it.
- Full reconciliation — every sync is a full pass over the selected spaces. Pages deleted in MCwiki (and spaces you deselect) are removed from the knowledge base. A partial MCwiki outage does not delete anything — deletions only happen when the remote read completed successfully.
Connecting MCwiki
- Open the Connectors dialog in your workspace and choose MCwiki (it appears under Knowledge Base).
- Enter the base URL and bearer token, then click Scan Spaces.
- Select the spaces to sync from the scan results.
- Click Connect. The first sync starts immediately.
| Field | Description | Example |
|---|---|---|
| Connector Name | A friendly name to identify this connection | MCwiki |
| MCwiki Base URL | The full URL of your MCwiki deployment (must be HTTPS unless an admin allows insecure HTTP) | https://mcwiki.example.com |
| Bearer Token | A token with access to the spaces you want to sync | <TOKEN> |
Periodic Sync
Periodic sync is on by default. Available frequencies: Every hour, Every 6 hours, Every 12 hours, Daily (default), or Weekly. The first sync always runs immediately after connecting, regardless of the schedule.
Self-hosted and private deployments
The connector requires HTTPS by default, and the base URL must not contain embedded credentials. Two administrator settings loosen that for trusted internal deployments. Both are stored in the config registry (DB-first: the stored value wins over the environment variable) and apply without a restart:
| Config key | Env fallback | Effect |
|---|---|---|
network.ALLOW_PRIVATE_MCWIKI_SERVERS | ALLOW_PRIVATE_MCWIKI_SERVERS | Permits MCwiki hosts on private, loopback, or link-local addresses |
network.ALLOW_INSECURE_MCWIKI_HTTP | ALLOW_INSECURE_MCWIKI_HTTP | Permits http:// base URLs, only for trusted local deployments |
These are separate from the A2A and MCP network toggles in the admin portal (Admin → System → Network), so enabling one integration does not widen the egress boundary for the others. Deployments that set PRIVATE_EGRESS_OVERRIDE_LOCKED cannot enable private egress at all.
Troubleshooting a sync
MCwiki sync is queued explicitly when you connect or re-run it. If the queue call fails, the connector is still saved and its config records a retry path — re-run the sync from the connector card with Sync now, or call POST /api/v1/search-source-connectors/{connector_id}/index?workspace_id={workspace_id}.