Connectors on human - The AI dev rig for AI coding agents

Jira

Mon, 01 Jan 0001 00:00:00 +0000

Connect to Jira Cloud or Jira Server.

Configuration

tracker: jira
jira:
  url: https://yourcompany.atlassian.net
  project: KAN
  token_env: JIRA_API_TOKEN
  email: you@example.com

Field	Description
`url`	Your Jira instance URL
`project`	Default project key
`token_env`	Environment variable containing your API token
`email`	Your Jira account email (required for Cloud)

Commands

# List issues in a project
human jira issues list --project=KAN

# Get a single issue with full details
human jira issue get KAN-1

# Create an issue
human jira issue create --project=KAN "Implement SSO"

# Add a comment
human jira issue comment add KAN-1 "This is done"

# List comments
human jira issue comments KAN-1

# Update issue status
human jira issue transition KAN-1 "In Progress"

Output format

human returns only the fields relevant for development — title, status, description, acceptance criteria, and comments. The output is structured for AI consumption with minimal token usage.

GitHub

Mon, 01 Jan 0001 00:00:00 +0000

Connect to GitHub Issues and Projects.

Configuration

tracker: github
github:
  project: octocat/hello-world
  token_env: GITHUB_TOKEN

Commands

# List issues
human github issues list --project=octocat/hello-world

# Get a single issue
human github issue get 42

# Create an issue
human github issue create --project=octocat/hello-world "Fix login bug"

# Add a comment
human github issue comment add 42 "Fixed in PR #43"

GitLab

Mon, 01 Jan 0001 00:00:00 +0000

Connect to GitLab Issues.

Configuration

tracker: gitlab
gitlab:
  project: mygroup/myproject
  url: https://gitlab.com
  token_env: GITLAB_TOKEN

Commands

# List issues
human gitlab issues list --project=mygroup/myproject

# Get a single issue
human gitlab issue get 42

# Create an issue
human gitlab issue create --project=mygroup/myproject "Add dark mode"

# Add a comment
human gitlab issue comment add 42 "Implemented in MR !15"

Linear

Mon, 01 Jan 0001 00:00:00 +0000

Connect to Linear issues and projects.

Configuration

tracker: linear
linear:
  project: ENG
  token_env: LINEAR_API_KEY

Commands

# List issues
human linear issues list --project=ENG

# Get a single issue
human linear issue get ENG-42

# Create an issue
human linear issue create --project=ENG "Implement feature"

# Add a comment
human linear issue comment add ENG-42 "Completed implementation"

Azure DevOps

Mon, 01 Jan 0001 00:00:00 +0000

Connect to Azure Boards work items.

Configuration

tracker: azuredevops
azuredevops:
  organization: myorg
  project: Human
  token_env: AZURE_DEVOPS_PAT

Commands

# List work items
human azuredevops issues list --project=Human

# Get a single work item
human azuredevops issue get 42

# Create a work item
human azuredevops issue create --project=Human "Set up CI pipeline"

# Add a comment
human azuredevops issue comment add 42 "Pipeline configured"

Shortcut

Mon, 01 Jan 0001 00:00:00 +0000

Connect to Shortcut stories.

Configuration

tracker: shortcut
shortcut:
  project: MyProject
  token_env: SHORTCUT_API_TOKEN

Commands

# List stories
human shortcut issues list --project=MyProject

# Get a single story
human shortcut issue get 42

# Create a story
human shortcut issue create --project=MyProject "Add user onboarding"

# Add a comment
human shortcut issue comment add 42 "Onboarding flow complete"

ClickUp

Mon, 01 Jan 0001 00:00:00 +0000

Connect to ClickUp tasks.

Configuration

Add a clickups: section to your .humanconfig.yaml:

clickups:
  - name: work
    token: pk_12345678_ABCDEFG
    team_id: "1234567"  # optional, for custom task IDs
    projects:
      - "901234567"     # List IDs

Field	Description
`name`	Instance name, used with `--tracker=<name>` when multiple trackers are configured
`token`	ClickUp personal API token (`pk_...`). Can also be set via `CLICKUP_TOKEN` or `CLICKUP_{NAME}_TOKEN` env var
`team_id`	Optional. Workspace ID, required when using custom task IDs (e.g. `PREFIX-123`)
`projects`	Optional. List of ClickUp List IDs to index
`url`	Optional. API base URL, defaults to `https://api.clickup.com/api`
`safe`	Optional. When `true`, blocks destructive operations (deletes)

ClickUp organizes work as Workspace > Space > Folder > List > Task. The --project flag maps to a List ID.

Notion

Mon, 01 Jan 0001 00:00:00 +0000

Connect to Notion workspaces — search pages, read content, query databases.

Configuration

notion:
  token_env: NOTION_TOKEN

Commands

# Search workspace
human notion search "quarterly report"

# Get a page
human notion page get <page-id>

Notion integration requires an internal integration token. Create one at notion.so/my-integrations and share the relevant pages with it.

Figma

Mon, 01 Jan 0001 00:00:00 +0000

Connect to Figma — browse files, inspect components, read comments, export assets.

Configuration

figma:
  token_env: FIGMA_TOKEN

Commands

# Get a file
human figma file get <file-key>

# List comments
human figma file comments <file-key>

# List components
human figma file components <file-key>

The output includes component structure, styles, and design tokens in a text format that AI agents can consume directly.

Amplitude

Mon, 01 Jan 0001 00:00:00 +0000

Connect to Amplitude — product analytics, events, funnels, retention, and cohorts.

Configuration

amplitude:
  token_env: AMPLITUDE_API_KEY
  secret_env: AMPLITUDE_SECRET_KEY

Commands

# List events
human amplitude events list

# List cohorts
human amplitude cohorts list

AI agents can query analytics data to inform implementation decisions.

Sentry

Mon, 01 Jan 0001 00:00:00 +0000

Connect to Sentry — error tracking, issue management, and event monitoring.

Configuration

sentry:
  organization: your-org-slug
  token_env: SENTRY_AUTH_TOKEN

Commands

# List issues in a project
human sentry issues list --project=your-project

# Get a single issue with details
human sentry issue get 12345

# List events for an issue
human sentry issue events 12345

# Resolve an issue
human sentry issue resolve 12345

# Unresolve an issue
human sentry issue unresolve 12345

AI agents can query Sentry issues to investigate errors and triage bugs during development.