Sign in and tokens
The two ways an assistant signs in to the MCP server, who can use them and how long they last.
On this page
An assistant reaches your organisation through a grant: an app you connected with OAuth, or a personal token you created. Both act as you and carry their own scopes, limits and expiry.
| OAuth connection | Personal token | |
|---|---|---|
| How you make it | Approve the app in your browser | Create token in the Control Panel |
| What the app holds | Its own short-lived access, renewed automatically | A token starting cfmcp_, shown once |
| Use it for | Claude, ChatGPT, Codex, Cursor, VS Code | Scripts and clients without OAuth |
Connect an AI assistant has the set-up for each client. MCP and API access has the Control Panel steps to create, change and remove a grant.
Who can use MCP
- You are a user of the organisation. Corefinity staff accounts are refused.
- Two-factor authentication is on for your account.
Both are checked on every request.
Lifetimes
| What | Lasts |
|---|---|
| Personal token, OAuth connection | Until the expiry you chose: see Limit a grant. |
| OAuth access token | 1 hour. The app renews it by itself while the connection lasts. |
| Approval page | 30 minutes to approve or deny. |
| Two-factor code | Asked for every new token and approval, and when you edit a grant. Not asked again for 15 minutes on the same grant, and never to rename or revoke one. |
An expired grant cannot be renewed: create a new token or approve the app again.
Rules
- Every user of the organisation sees every token and connected app.
- Only the person who created a grant, or an owner of the organisation, can edit or revoke it.
- Approving an app you have already connected updates that connection. It does not add a second one.
- One person can hold up to 100 active tokens and apps.
- An MCP token works only at the MCP server address. The REST API uses its own tokens: see Authentication.
Was this helpful?