Providers

Agent Workflows separates where work is managed from where code is delivered. Configure one provider for each responsibility; workflows route every operation to the integration selected by the project.

Work items: ClickUp or Linear

The item provider owns ticket lookup, creation, comments, labels, and status changes. Approved plans are published and read through the same provider boundary.

mcp:
  item:
    provider: linear # or clickup

Code delivery: GitHub or GitLab

The version provider owns branches, commits, pull or merge requests, and reviews.

mcp:
  version:
    provider: github # or gitlab

The mcp.version.provider key is retained for existing project configurations; github selects the gh CLI.

Configure provider access

ClickUp operations use the community clickup-cli directly. Install it and configure the API token and Workspace before selecting ClickUp:

clickup-cli setup

Run the setup command in the agent’s execution environment. The provider contracts call clickup-cli directly.

Linear operations use the community schpet/linear-cli directly. Install it and authenticate it with a Linear API key before selecting Linear:

linear auth login

The provider contracts use native linear commands and linear api for focused GraphQL queries. The mcp.item.provider key is retained for existing project configurations; clickup and linear select their respective CLIs.

GitHub operations use the official gh CLI. Install it and authenticate it for the repository’s host before selecting GitHub:

gh auth login --hostname github.example.com

For GitHub.com, use gh auth login.

GitLab operations use the official glab CLI instead of an MCP server. Install it, then authenticate it for the repository’s host before selecting GitLab:

glab auth login --hostname gitlab.example.com

For GitLab.com, run glab auth login.