CircleCI
Where to apply for a CircleCI personal API token, which permissions it carries, and how to connect it to Nora.CircleCI integrations let your agents trigger pipelines, read build status, and inspect workflow runs. Nora authenticates with a personal API token via the
Circle-Token header — the same scheme circleci CLI uses.
Where to apply for credentials
Personal API tokens are managed from your user settings:CircleCI Personal API Tokens
Required permissions
CircleCI personal tokens inherit the permissions of your user account — there are no separate scope checkboxes. If your CircleCI account can read the projects you want the agent to act on, the token can too. For org-owned projects, make sure your account is a member of the relevant organization.Connect in Nora
Open the CircleCI integration
From an agent’s detail page, open the Integrations tab and find CircleCI in the catalog.
Verify the connection
The Test button callsGET /api/v2/me. Common failures:
- 401 Unauthorized — token revoked. Generate a new one from the same page.
- 403 Forbidden — token belongs to a user that no longer has access to the org.
MCP server
No official MCP server. The token is exposed to the agent asCIRCLE_TOKEN so any community MCP server reading that env var works.
Environment variables Nora injects
| Variable | Source |
|---|---|
CIRCLE_TOKEN | Personal API Token field |