Krosoft Wiki
Auto Light Dark
Auto Light Dark

Configure MCP policies

For Confluence administrators. These settings restrict MCP access without granting Confluence permissions.

1. Open MCP policies

Open Confluence administration → MCP policies, or Manage apps → Configure for the app. Complete Confluence’s secure-session confirmation if requested. A REST PAT does not establish that browser session. Use the section links to jump to Space access, OAuth clients, Audience, MCP mode or Rate limit. Expand the help text in each section for details. The Effective configuration overview shows the active settings and links to each section. Unsaved edits do not change it. Select Documentation in the page header to open the product guide in a new tab while keeping your configuration edits on screen.

2. Choose policies

Setting

Choose

Who may use MCP

Keep All authenticated users (default), or choose Selected users and groups to enter usernames and groups. Those fields apply only to the selected audience. An empty selection admits nobody, including administrators.

MCP mode

Keep Read and write (default), or select Read only to prevent content changes through MCP.

Space policy

Keep Native permissions (default), or use an Allowlist or Blocklist.

Request rate limit

Default: 300 requests per minute per user per node, with a burst of 100. Adjust only when needed.

Audience and rate input limits

Audience selection accepts up to 200 usernames and 100 group names. Unknown entries are rejected. Group membership follows Confluence’s directory synchronization and caching. The administration screen remains available to administrators even when their MCP access is excluded.

Rate fields accept whole numbers: 1 through 6,000 requests per minute and a burst of 1 through 1,000. Restore default rate limit restores 300 and 100. Remove saved MCP audience restores access for all authenticated users; Remove saved MCP mode restores read and write. Review the displayed effects and tick the confirmation checkbox before resetting.

Space policy

Space modes and input rules

Mode

Effect

Native permissions

No extra space filter. Space keys is hidden; saving clears both lists.

Allowlist

Only listed spaces are eligible.

Blocklist

Listed spaces are excluded, including for administrators.

For Allowlist or Blocklist, enter 1 through 20 distinct comma-separated space keys, at most 6,000 input characters. Keys are case-sensitive; personal spaces such as ~username are supported. Select Save space policy. Changing modes replaces the previous list. Invalid input leaves the policy unchanged.

3. Save and check

Save each changed form independently using Save MCP audience, Save MCP mode, Save space policy or Save rate limit. With JavaScript, edited forms show Unsaved changes; a warning lets you cancel navigation or another form action that would discard edits. Without JavaScript, save one form before editing another. Changes apply to subsequent requests without a restart. Check the effective overview and verify that intended users can connect and restrictions behave as intended.

For OAuth access, follow Configure OAuth for MCP clients. For enforcement rules and per-operation permissions, see Security and permissions.

Existing JVM configuration

JVM fallbacks and saved-policy precedence

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 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.

File transfer configuration

Transfer size and temporary storage

The file-transfer default is 10 MiB. To change it, set native.mcp.maxTransferBytes to 32,768 through 104,857,600 bytes and restart the app/node. Native upload restrictions and site limits still apply.

Provide writable private temporary storage separately from Confluence attachment storage. A process crash can leave temporary files requiring administrator cleanup. Native backup and retention rules still apply.

Size, session and reservation limits, expiry and node affinity are in Transfer capacity and deployment constraints.

Direct administration URL

<confluence-base-url>/plugins/servlet/native-mcp/admin

For problems, see Policy troubleshooting.