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 enables task management across both platforms.
Features
| Feature | Description |
|---|---|
| OAuth 2.0 and Basic Auth | Flexible authentication options |
| Automatic Task Syncing | Keep tasks in sync between AgentLoop and Jira |
| AI-Powered DAG Planning | Generate task dependencies from Jira issues |
| Sprint and Board Management | Sync with Jira sprints and boards |
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"Jira Commands
Interactive Mode
| Command | Description |
|---|---|
/jira sync | Bidirectional sync with Jira |
/jira sync-dag | AI-powered sync with dependency analysis |
/jira status | Show Jira integration status |
/jira authorize | Perform OAuth authorization |
Authentication Methods
Basic Auth
Basic Auth is simpler to set up:
- Generate an API token in Jira (Settings → Security → API tokens)
- Configure in AgentLoop:
> /jira set-auth user@example.com your-api-tokenOr in config:
[jira]
email = "user@example.com"
apiToken = "your_api_token"Syncing Tasks
Basic sync:
> /jira syncAI-powered sync with dependency analysis:
> /jira sync-dagThe DAG sync analyzes Jira issues and automatically creates dependencies based on issue links and relationships.
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 IDGitHub Integration
GitHub integration enables automated PR creation and branch management.
Configuration
[github]
enabled = true
token = "ghp_your_token_here" # Or use environment variableOr use an environment variable:
export GITHUB_PERSONAL_ACCESS_TOKEN="ghp_your_token_here"Required Token Scopes
The GitHub Personal Access Token needs these scopes:
repo- Full control of private repositoriesworkflow- Update GitHub Action workflows (if using CI/CD)
Features
When GitHub is configured, engineer agents can:
- Create branches for tasks
- Commit and push changes
- Create pull requests
- Update PR descriptions
MCP Integration
Model Context Protocol (MCP) allows AgentLoop to integrate with external tools and services.
What is MCP?
MCP is a 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
Configuration
MCP servers are configured in your AgentLoop config. See the MCP documentation for specific server configurations.
Plugin System
AgentLoop’s plugin system supports:
- Custom agent templates - Create agents with specific behaviors using markdown
- Three-layer configuration - Build-time, runtime, and per-project settings
- MCP integration - Connect to external MCP servers
Configuration Reference
Jira Settings
| Option | Description |
|---|---|
siteUrl | Jira site URL (e.g., https://company.atlassian.net) |
project | Jira project key (e.g., PROJ) |
boardId | Board ID for accurate syncing (find in board URL) |
email | Email for Basic Auth |
apiToken | API token for Basic Auth |
clientId | OAuth client ID (set via command) |
clientSecret | OAuth client secret (set via command) |
GitHub Settings
| Option | Default | Env Variable | Description |
|---|---|---|---|
enabled | true | - | Enable GitHub integration |
token | - | GITHUB_PERSONAL_ACCESS_TOKEN | GitHub PAT |
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"Never commit API tokens or secrets to version control. Use environment variables for sensitive credentials.