Install and configure | Krosoft Wiki

For Confluence administrators installing the plugin and managing optional space restrictions.

Available tools

The app supports page editing, comments, labels, history, attachments, navigation and page lifecycle operations. Refresh tool discovery after changing the connection; tools/list lists the operations available to the caller under native permissions and administrator policies.

Install the app

Review Compatibility and limitations and obtain the appropriate package from Krosoft for your Confluence version and agreed offering. Use confluence9.jar for the Confluence 9 package or confluence10.jar for Confluence 10; choose the package matching your Confluence major version. A valid Confluence Data Center license is required separately.
Open Confluence administration → Manage apps and install the package using the site’s app installation process. Where UPM verifies signatures, use the supplied signature for that exact package and trust the approved supplier certificate through your site’s installation process. Confirm the app is enabled.
Provide users with <confluence-base-url>/rest/native-mcp/1.0/mcp, including the site’s context path. Use HTTPS. Each user supplies their own Confluence credentials.

The Confluence server must also be able to reach its configured base URL for search. Its JVM must trust that URL’s certificate, and any proxy must preserve caller authentication.

Optional space policy

By default, MCP follows the caller’s native space and page permissions. No list is required. Open Confluence administration → MCP policies, or the app’s Configure action in Manage apps. The direct path is <confluence-base-url>/plugins/servlet/native-mcp/admin.

Mode	Effect
Native permissions	No extra space filter. Space keys is hidden; saving clears both lists.
Allowlist	Only the listed space keys are eligible. Native permissions still apply.
Blocklist	Listed space keys are excluded, including for administrators.

For Allowlist or Blocklist, enter 1–20 distinct comma-separated space keys, up to 6,000 input characters. Keys are case-sensitive; personal-space keys such as ~username are supported. Select Save space policy. Changes apply to subsequent operations without a restart. Changing modes replaces the previous list. Invalid list input is rejected without changing the policy.

Use the native administration screen and complete any Confluence secure-session challenge. Only Confluence administrators can save policy. Filters restrict eligible spaces; they never grant permission to read or write a page.

Existing JVM configuration

Until the first administrator save, native.mcp.allowedSpaces and native.mcp.blockedSpaces are optional JVM fallbacks. Missing or blank values add no restriction. After a save, the saved policy overrides both properties, including when Native permissions is selected.

A legacy combined policy is displayed read-only until an administrator selects and saves a replacement mode. In a combined policy, blocklist takes precedence. Malformed or unreadable policy fails closed; repair it through the administration screen.

Deployment and diagnostics

Use Confluence and proxy controls for deployment-wide request size, timeouts and concurrency. Configure the app’s per-user request rate and burst limit in MCP policies; streaming has additional per-node and per-caller limits. See Compatibility and limitations for request, streaming and cluster limits.

The authenticated /rest/native-mcp/1.0/mcp/info endpoint reports the executing user and effective space policy. Empty policy lists mean no administrator filter; they are not a list of the user’s accessible spaces. readOnly: false means write tools exist, not that every caller can write.

Next steps

Share Connect your MCP client with users. For maintenance, use Upgrade and uninstall; for operational problems, use Troubleshooting | For Confluence administrators.

Permissions and limits

All operations use the caller’s native permissions and administrator space policy. See Security and permissions for per-action access rules and Tools for arguments and file limits.

These operations follow the same native permissions and administrator policies as other tools.

Action	Native access and operational effect
Space/page navigation	Native space and page VIEW plus administrator policy on every path edge. No hidden totals or paths. Personal spaces follow the same rules.
File upload/version/copy	Current owning-page and attachment visibility; native attachment-create/update rules and site restrictions. Both copy endpoints must pass policy. Native history/editor attribution applies to explicit new versions. Existing create-only operations retain their 32 KiB limit.
Page/tree copy	Every source and ancestor must be visible and unrestricted; destination page/space visibility and page-create permission. Refuses inaccessible descendants. Copies inherit destination access; labels/files are explicit. Original links/macros are retained. Comments, properties and history are excluded. Earlier copied items may remain if a later item fails.
Move/reorder	Native action-specific move permission, source edit/destination create rules, both policies and full bounded-subtree access. Same-space only. Page identity and direct restrictions remain; inherited access follows the destination.
Trash	Native per-page REMOVE and native trash validation. Current non-homepages without children only. Reversible; no recursive trash or permanent purge.
Trash discovery/restore	Requires native space administration, visibility and restoration permission, plus a valid same-space destination. Title, state and destination-access conflicts are refused.

File transfers default to 10 MiB. Set native.mcp.maxTransferBytes to 32,768–104,857,600 bytes and restart the app/node to change it; native upload limits still apply. Allow writable private temporary storage for up to 16 pending sessions per node, four per caller and 128 MiB of declared reservations per node. Sessions expire after 15 minutes. A process crash may leave temporary files requiring administrator cleanup.

Use node affinity for pending transfers and navigation cursors; restarting the app invalidates them. Plan temporary storage separately from Confluence attachment storage. Native backup and retention rules still apply. Inspect saved content after uncertain operations and validate capacity and failover for your deployment.

Pending page copies

Page copies use single-use continuations with node affinity. They allow at most 16 pending plans per node and four per caller, expiring after 15 minutes. Changed permissions or content can stop remaining work. Cancelling keeps pages already copied; inspect saved results before retrying.