Read CircleCI Cloud organization projects and pipeline identities with your personal API token using API v3. UUIDs and opaque cursors follow the current official API. Each invocation makes one request, without retries, automatic paging or polling. This subset excludes pipeline execution, cancellation, configuration, environment variables and logs. CircleCI Server and managed OAuth are not supported by this connection.
What you can do (3)
What you can do
Available commands: 3 (3 read, 0 write). Enable only the commands your application needs.
| Command | Effect |
|---|---|
List organization projects — circleci.projects.list |
Read |
List project pipeline IDs — circleci.pipelines.list |
Read |
Get a pipeline summary — circleci.pipelines.get |
Read |
Connect and use
Open the integration's connection form to check the available credential source. The source has not been resolved for this documentation export. The instructions below apply when using your own provider account.
Get your provider credentials
Follow these steps for CircleCI, then enter the issued values in the connection form below.
- In CircleCI User Settings open Personal API Tokens, create a named token with an expiry date, and copy it when shown. Enter it in CircleCI personal API token in this connection. Manually created personal tokens can have broad read/write permissions, so use a dedicated least-privilege account; these Tooluse.net commands only read. Project API tokens and CircleCI Server are not supported by this Cloud v3 connection. Find your organization UUID in Organization Settings, list its projects, then use a project UUID to list pipeline IDs and read a pipeline summary. Include the project UUID for a synthetic OAuth pipeline lookup. Copy project cursors unchanged for the next page. Select only needed commands, save, and create a scoped Tooluse.net API key for your client. Replace an expired or revoked provider token in the same connection; this form does not provide managed OAuth or automatic token refresh.
Where to enter credentials
In the integration page, sign in, choose your workspace and open Connect. If a Credentials choice is shown, select Use my credentials. Fill the following connection fields and save. Provider credentials belong in this form, never in an MCP configuration or tool input.
| Connection field | Requirement |
|---|---|
| CircleCI personal API token | Required |
Open API keys and create a Tooluse.net key for the enabled commands.
Set TOOLUSE_API_KEY in your client and use the shared MCP configuration.
Configure Claude Code, Codex or Cursor once
Permissions and results
If you have more than one workspace, check the selected workspace in the connection or API-key dialog before saving. Roles, enabled commands, expiry and revocation use Tooluse.net's existing permissions. Disabling a connection or revoking a key immediately prevents new calls.
Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.
Your connection's daily allowance and key permissions also apply. Adding a connection does not make a provider request.
Calls return the shared execution receipt and a Claude tool_result. Provider output varies by operation; consult the provider documentation for its response fields. Unconfirmed calls should be checked before retrying.
Call from your client
Use the shared MCP configuration. Refresh your client's tool list after saving the connection or changing key permissions, then call the returned tool name with the example input below.
Configure Claude Code, Codex or Cursor once
Discover your enabled tools
List permitted tools in Claude format. Read every page using page and size (maximum 100) until all results have been received. Use the returned name, not a catalog capability identifier, in the tool_use block.
curl 'https://api.tooluse.net/v1/tools' \
-H "Authorization: Bearer $TOOLUSE_API_KEY"
Find this command in the tool list permitted by your key. Replace svc_FROM_YOUR_TOOL_LIST with its returned name. Use a new Idempotency-Key for each new call and retain it when retrying that same call.
HTTP call
curl 'https://api.tooluse.net/v1/tool-calls' \
-H "Authorization: Bearer $TOOLUSE_API_KEY" \
-H 'Content-Type: application/json' \
-H 'Idempotency-Key: replace-with-a-new-call-id' \
--data '{
"type": "tool_use",
"id": "toolu_example",
"name": "svc_FROM_YOUR_TOOL_LIST",
"input": {
"query": {
"filter[org_id]": "c6e2e2cd-d0ee-4253-be29-d076f9555602",
"page[limit]": 20
}
}
}'
Send one Claude tool_use block per request. Keep the same Idempotency-Key when retrying the same request; use a new key for a new call. The response includes the shared Tooluse.net receipt and Claude tool_result. Check both HTTP status and the returned tool result before treating a call as successful.
Commands
List organization projects — circleci.projects.list
Read one explicit page of CircleCI Cloud projects in an organization your personal token can access. Returns project UUIDs, names, following status, organization UUIDs and opaque next/previous cursors. Copy a cursor unchanged into the next call; no automatic paging. Does not read settings, environment variables or trigger builds.
This is a read operation. Provider rate limits and data access rules still apply.
Parameters
Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.
| Parameter | Type | Required in parent | Description | Constraints |
|---|---|---|---|---|
query |
object | Required | additionalProperties: false |
|
query.filter[org_id] |
string | Required | Organization UUID from CircleCI Organization Settings; not an organization slug. | format: "uuid" |
query.page[limit] |
integer | Required | Maximum projects in this page. The official v3 endpoint permits at most 50. | minimum: 1; maximum: 50 |
query.page[cursor] |
string | Optional | Opaque next or previous cursor from an earlier projects result. Omit for the first page; do not decode it or supply a URL. | minLength: 1; maxLength: 4096 |
Full JSON Schema
Example input
{
"query": {
"filter[org_id]": "c6e2e2cd-d0ee-4253-be29-d076f9555602",
"page[limit]": 20
}
}
At most 1 provider requests per invocation; timeout: 30 seconds.
List project pipeline IDs — circleci.pipelines.list
Read pipeline UUIDs for one CircleCI Cloud project. Use a project UUID from projects.list, then pass a returned pipeline UUID to pipelines.get. The official endpoint does not expose pagination parameters; this command makes one request and refuses a response above the existing 512 KiB transport bound. It does not trigger pipelines or return configuration.
This is a read operation. Provider rate limits and data access rules still apply.
Parameters
Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.
| Parameter | Type | Required in parent | Description | Constraints |
|---|---|---|---|---|
query |
object | Required | additionalProperties: false |
|
query.filter[project_id] |
string | Required | Project UUID from projects.list; project slugs are not accepted by v3. | format: "uuid" |
Full JSON Schema
Example input
{
"query": {
"filter[project_id]": "f4b4e6cc-8568-426b-b750-4d2b57df7f01"
}
}
At most 1 provider requests per invocation; timeout: 30 seconds.
Get a pipeline summary — circleci.pipelines.get
Read the UUID, name, creation time and project UUID of one CircleCI Cloud pipeline. Supply filter[project_id] from the listing request when resolving a synthetic OAuth pipeline; the provider requires its project context. Configuration, checkout details, repository credentials, logs and writes are excluded.
This is a read operation. Provider rate limits and data access rules still apply.
Parameters
Requiredness is local to the containing object. A required child is required only when its parent object or array item is provided. Alternative schemas are identified in the Constraints column; the linked full JSON Schema is authoritative.
| Parameter | Type | Required in parent | Description | Constraints |
|---|---|---|---|---|
path |
object | Required | additionalProperties: false |
|
path.id |
string | Required | Pipeline UUID returned by pipelines.list. | format: "uuid" |
query |
object | Optional | additionalProperties: false |
|
query.filter[project_id] |
string | Required | Project UUID used for pipelines.list. Required by CircleCI for synthetic OAuth pipeline lookups, optional for stored pipelines. | format: "uuid" |
Full JSON Schema
Example input
{
"path": {
"id": "e7b6b195-e223-4651-98b9-44f734b20f1a"
},
"query": {
"filter[project_id]": "f4b4e6cc-8568-426b-b750-4d2b57df7f01"
}
}
At most 1 provider requests per invocation; timeout: 30 seconds.
Errors
Check the key's expiry, revocation, workspace and allowed operations.
Reuse the same idempotency key only for the same request.
The connection or provider limit has been reached. Check the receipt before retrying.
Test the connection
Open the integration's commands below to inspect parameters and examples. Start with a read command for an account or resource you can access. Refresh your client's tool list, use the returned tool name, and check the execution result and usage. Provider charges and permissions still apply. Never test a write against production data without reviewing it.