The CircleCI connector.
Pipelines, workflows and job status. Connect once with your own key. Every agent your team runs reads the same 5 tools under one permission model.
How access is governed
5
Read tools
Open by default. They run when called, and every call is logged with the endpoint, tool and capability.
0
Write tools
CircleCI exposes no write tools. Nothing it does mutates external state.
0
Destructive tools
CircleCI defines no destructive tools. Nothing here deletes data.
Defaults come from the capability on each tool definition, and an admin can tighten or open any tool individually. The endpoint's capability ceiling can only tighten that policy. An endpoint scoped to read never surfaces a write tool.
Every CircleCI tool
5 tools, named as the agent sees them.
- list_pipelinesread
List recent pipelines for a project. Start here: the project slug is "vcs/org/repo" (e.g. "gh/acme/app"). The returned pipeline `id` feeds get_pipeline and list_workflows.
- get_pipelineread
Get one pipeline by its uuid, as returned in the `id` field of list_pipelines.
- list_workflowsread
List the workflows in a pipeline, with their pass/fail status. Takes the pipeline uuid from list_pipelines; the returned workflow `id` feeds list_workflow_jobs.
- list_workflow_jobsread
List the jobs in a workflow — use this to find which job failed. Takes the workflow uuid from list_workflows; the returned `job_number` feeds get_job.
- get_jobread
Get one job’s detail, including duration and its web_url for the full logs. Takes the project slug used in list_pipelines and the `job_number` from list_workflow_jobs (the integer, not the job uuid).
Use it from any agent
The same CircleCI tools reach Claude Code, Cursor, Claude Desktop or your own agent through one MCP endpoint. The endpoint is scoped to a group, the token is issued per group and revocable from the dashboard, and an allowed-tool list and capability ceiling limit what it exposes. Reads run. Gated writes refuse unless an admin opens them. Destructive tools remain unavailable over MCP.
{
"mcpServers": {
"growth": {
"type": "http",
"url": "https://app.notara.ai/mcp/g/acme/growth",
"headers": {
"Authorization": "Bearer ntr_mcp_xxxxxxxxxxxxxxxxxxxx"
}
}
}
}The URL and token are placeholders. Real endpoints are issued per group from the dashboard.
Setup
- 01
Create a CircleCI Personal API Token in your CircleCI account (where to find it). The key is yours: Notara stores it encrypted and never sees a bill.
- 02
Paste it into the Notara dashboard. Credentials can be scoped to the workspace or to one person.
- 03
The tools appear with their capability defaults already set. Tighten or open any of them per tool, then invite the agent to a channel or issue an MCP token.
Connect CircleCI once. Use it everywhere.
Use Notara directly, or bring us the workflow that needs to be redesigned and built.