Integrations

AgentLoop integrates with external services to enhance your development workflow. This page covers Jira, GitHub, and MCP (Model Context Protocol) integrations.

Jira Integration

Bidirectional synchronization with Jira Cloud keeps tasks aligned across both platforms.

Features

Configuration

Add Jira settings to your config file:

[jira]
siteUrl = "https://yourcompany.atlassian.net"
project = "PROJ"
boardId = "123"
 
# Basic Auth (simpler)
email = "user@example.com"
apiToken = "your_api_token"

Authentication Methods

Syncing Tasks

Once Jira is configured, you can ask AgentLoop in chat to sync:

Sync with Jira.

Pull in any new Jira tasks for this project.

The AI-powered DAG sync analyzes Jira issue links and infers dependencies between tasks automatically.

Finding Your Board ID

The board ID is needed for accurate syncing. Find it in your Jira board URL:

https://yourcompany.atlassian.net/jira/software/projects/PROJ/boards/123
                                                                     ^^^
                                                                  Board ID

GitHub Integration

GitHub integration enables automated PR creation and branch management by the release agent.

Configuration

[github]
enabled = true
token = "ghp_your_token_here"   # Or use environment variable

Or use an environment variable:

export GITHUB_PERSONAL_ACCESS_TOKEN="ghp_your_token_here"

Required Token Scopes

The GitHub Personal Access Token needs:

• repo — Full control of private repositories
• workflow — Update GitHub Action workflows (if your project uses them)

What GitHub Integration Enables

When GitHub is configured, agents can:

• Create branches for tasks
• Commit and push changes
• Open pull requests as the release agent
• Update PR descriptions with task context

MCP Integration

Model Context Protocol (MCP) lets AgentLoop integrate with external tools and services.

What is MCP?

MCP is an open protocol for extending AI agents with external capabilities. AgentLoop can use MCP servers to:

• Access external APIs
• Query databases
• Interact with third-party services
• Use custom tools you’ve built

Bundled MCP Server

AgentLoop ships its own MCP server so other agentic tools (like Claude Code, Cursor, or VS Code extensions) can talk to AgentLoop. This means you can drive AgentLoop tasks from another tool that speaks MCP.

External MCP Servers

You can also configure external MCP servers for your agents to use. The configuration lives in your AgentLoop config — see the Configuration panel in the desktop app.

Plugin System

AgentLoop’s plugin system supports:

• Custom agent templates — Define new agents with specific behaviors using markdown templates
• Layered configuration — Build-time, runtime, and per-project settings
• MCP integration — Connect to external MCP servers

Configuration Reference

Jira Settings

GitHub Settings

Example Configuration

Complete integration setup:

# GitHub
[github]
enabled = true
 
# Jira
[jira]
siteUrl = "https://mycompany.atlassian.net"
project = "DEV"
boardId = "42"
email = "developer@mycompany.com"
apiToken = "your-jira-api-token"