Requirement Details
Hi @santhoshkumar_sethi, nothing to acquire from Atlassian, your own org admin makes one. Atlassian Administration, Directory, Service accounts, Create a service account, then give it the Confluence role. No seat cost, they don't count towards your user limit.
Then pick the account, Create credentials, API token, set an expiry between 1 and 365 days, and tick only the read Confluence scopes. Scopes are frozen once the token exists. A wrong pick means a new token.
Read-only isn't the scopes alone. Service accounts sit under the same permission requirements as a user account, so put it in a group that only has view rights on the spaces you want reachable.
If it's Atlassian's own Rovo MCP server you're pointing at, a service account key goes in as a Bearer token. Basic auth with the base64 email and token is for personal tokens.
Manage API tokens for service accounts
It looks like you're new here. Sign in or register to get started.
