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. |
Space policy
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
File transfer configuration
For problems, see Policy troubleshooting.