MCP keys and sign-in

Agents connect to Roar's MCP server with an API key (a secret starting with roar_sk_) or by signing in to Roar through OAuth. Either way, the connection is limited to one workspace and one scope.

Scopes#

Neither scope can delete or untrack posts, or change billing or team settings. Use Read for reporting.

Creating a key#

Only owners can create and revoke keys. Members see "Owner access required."

1. Open Settings → Developers.
2. Under MCP keys, enter a Key name that identifies where the key will be used, such as "Work laptop".
3. Choose Read or Read and write.
4. Select Create key.
5. Copy the secret. It's only shown once.

The same window shows a Claude Code command and a Cursor config with the secret filled in.

Storing keys#

• Anyone with a key can use your workspace with that key's scope.
• Store keys in an environment variable (for example ROAROS_API_KEY) or your client's secret store, not in a file you commit.
• Create a separate key for each machine or script, so you can revoke one without affecting the others.

Revoking a key#

Settings → Developers lists each key's name, scope, last use, and creation date. Choose Revoke and confirm to disable a key immediately. Revoking can't be undone.

Keys also stop working when the person who created them leaves the workspace. Before removing an owner, have another owner create replacement keys.

OAuth sign-in#

Claude.ai and Cursor can connect without a key. When you add Roar's endpoint, the client opens a Roar sign-in and consent screen.

1. Check that the screen names the app you're connecting.
2. Choose Read or Read and write.
3. Select Approve, or Deny.

The connection uses the workspace you're signed in to. To change its scope, remove the connector in your client and connect again.

Limits#

Calls count toward your workspace's daily MCP limit however the agent connects: 500 a day on Individual, 2,000 on Pro. See Plans and usage.