List projects

list_projects List the website projects this credential can access.

Available in the deployed MCP and HTTP bundle. Confirm access and inputs with your connected catalog. Workspace scopes and enabled providers still apply.

Access	Behavior
`projects:read`	Reads saved data

This read does not start a verification job.

Example request

Connect through MCP, CLI, or HTTP. Replace example identifiers with records from your workspace.

{
  "jsonrpc": "2.0",
  "id": 1,
  "method": "tools/call",
  "params": {
    "name": "list_projects",
    "arguments": {}
  }
}

agentlinkops call list_projects --args '{}'

curl "$AGENTLINKOPS_API_URL/v1/commands/list_projects" \
  -H "Authorization: Bearer $AGENTLINKOPS_API_KEY" \
  -H 'Content-Type: application/json' \
  --data '{}'

Returned result

Illustrative data validated against the documented response schema. IDs and dates are examples, not a live account capture. MCP returns this data in structuredContent and in a text content block; generic HTTP and CLI return the JSON result directly.

{
  "items": [
    {
      "id": "pr_example",
      "workspace_id": "ws_example",
      "name": "Example project",
      "domain": "example.com",
      "created_at": "2026-09-13T12:00:00.000Z"
    }
  ],
  "next_cursor": null
}

Input fields

Omit optional fields when you do not want to supply them. Null is accepted only where listed. Unknown input properties are rejected.

Field	Type	Presence	Meaning and constraints
`cursor`	string	Optional	Opaque continuation returned by this same listing; omit for the first page.
`limit`	integer	Optional	Maximum rows in this page or bounded report; subject to the schema maximum. minimum: 1; maximum: 100; default: 50

Validation and omitted values

Omit cursor for the first page. Keep continuation cursors opaque and use them only with the same listing and filters. Pages are ordered by creation time, then identifier, ascending.

Defaults when omitted

Field	Default
`limit`	`50`

Output fields

Fields inside optional or nullable parents apply only when that parent exists. Common schema conventions explain evidence states, empty lists and extensions.

Field	Type	Presence	Meaning and constraints
`items`	array	Required	Records in this bounded page.
`items[].id`	string	Required	Resource identifier returned by the operation.
`items[].workspace_id`	string	Required	Workspace that owns this record.
`items[].name`	string	Required
`items[].domain`	string	Required
`items[].created_at`	string	Required	UTC timestamp when the record was created.
`items[].created`	boolean	Optional	True when this request created the record; false when an existing record was reused.
`next_cursor`	string / null	Required	Opaque continuation for the same listing; null means no further page.
`has_more`	boolean	Optional	True when another page is available.

Download input schema · Download output schema

Errors and retries

The command is annotated idempotent. Reuse an accepted idempotency key when the input provides one; changing the payload under a reused key can conflict. Operation-specific errors include UNAUTHORIZED, INSUFFICIENT_SCOPE, WORKSPACE_ACCESS_DENIED, INVALID_GRANT, INVALID_LIMIT, INVALID_CURSOR. See error recovery for status, scope, cooldown, cursor and retry handling. Unknown observations are result data and do not establish loss.

HTTP resource routes

These existing resource routes share the operation’s domain behavior. Their parameter placement, status and response envelope can differ from generic invocation. See HTTP route details.

Method and route	Success	Details
`GET /v1/projects`	200	Remaining read arguments go in query parameters.

Continue

get_project · get_workspace Follow the related workflow, inspect capability status, or return to the command index.

Overview

MCP, CLI and API commands

CLI client

HTTP and events

Optional local workflows

Example request

Returned result

Input fields

Validation and omitted values

Defaults when omitted

Output fields

Errors and retries

HTTP resource routes

Continue

​Example request

​Returned result

​Input fields

​Validation and omitted values

​Defaults when omitted

​Output fields

​Errors and retries

​HTTP resource routes

​Continue

Example request

Returned result

Input fields

Validation and omitted values

Defaults when omitted

Output fields

Errors and retries

HTTP resource routes

Continue