Krosoft Wiki
Auto Light Dark
Auto Light Dark

MCP for Confluence Data Center - Troubleshooting

Start with your role. Follow the linked guide for the detailed procedure.

Users

Problem

Next step

Cannot connect

Check your site address and network access, then follow your client setup guide. Renew OAuth sign-in or replace an expired PAT as appropriate.

Wrong account

Ask the assistant to verify its connected Confluence account, then reconnect with the intended account.

Missing pages

Check whether your account can open the page in Confluence. Search can lag recent changes; MCP policy can further restrict access. See Access rules.

Cannot save changes

Native permissions, OAuth scopes or read-only mode can block writes. For incomplete reads or conflicts, read the current page again or use Confluence’s editor. See Write permissions.

Administrators

Problem

Next step

Access or policy problem

Review Configure MCP policies. Invalid input leaves the policy unchanged; unreadable access settings restrict access until repaired through the administration screen.

Policy screen cannot open or save

Use a native administrator browser session and complete its secure-session challenge. Reload before saving; a REST PAT alone does not establish that session.

OAuth unavailable or client refused

Check OAuth settings and client access.

Search fails but page reads work

Check base-URL reachability, JVM certificate trust and forwarded authentication in Deployment checks.

JVM settings have no effect

A saved space policy overrides the space-filter JVM properties. See JVM configuration.

Diagnostics

Request references and logging

Handled responses include X-MCP-Request-ID; tool errors include requestId and errorCategory. Use the reference and request time to locate app diagnostics in atlassian-confluence.log. Authentication or routing failures before the app runs may have no MCP reference.

For a short investigation, set nl.krosoft.confluence.mcp.McpDiagnostics to DEBUG in Confluence Logging and Profiling, then restore the previous level. App events include the reference, operation, status, category and duration without usernames, credentials, queries or page content.

Technical users

Problem

Next step

HTTP 400, 401 or 404

Check the endpoint, protocol and authentication in Connection contract. Use the MCP endpoint, not /info; 404 can also mean the app is disabled.

HTTP 403

Check audience/native access and any supplied Origin header, which must match Confluence’s configured origin. See Access enforcement.

Failed tool call or invalid arguments

Inspect isError and the error object; HTTP 200 alone is not tool success. Use the current tools/list schemas and Tool contracts.

File, section or version rejection

Check Editing and tool-specific rules and Operational limits.

Timeout or partial result

Inspect mutationOutcome, retryGuidance and saved native state before retrying. See Errors and retries.

HTTP 429

Wait for Retry-After; see Request limits.

Get help

Contact the Krosoft Support Portal or support@krosoft.nl for support or security reports.

Include the request time, app/Confluence/Java/UPM/client versions, sanitized error and request reference when available. State whether the same account can access the content directly in Confluence. Do not include tokens, cookies, full page bodies or restricted content; share only the minimum diagnostic detail.

Hours, response aims and support scope are in the Krosoft support policy. Supported platforms and operational scope are in Compatibility and limitations.