# Concord MCP for AI Agents AI Agent Connect

> Concord MCP for AI Agents. Let your agent manage CI/CD workflows, check execution logs, and browse your Concord organization directly from your chat interface. It connects your agent to your self-hosted Concord instance so you can handle process management without leaving your workspace.

## Overview
- **Category:** industry-titans
- **Price:** Free
- **Endpoint:** https://edge.vinkius.com/vk_preview_Zu1FtaypR6vodFhZs1KNTeO3BBzUOEVSxrwO3xgK/ai-agent-connect
- **Tags:** workflow-orchestration, ci-cd, process-automation, log-analysis, pipeline-management

## Description

The Concord MCP connects your AI agent to your self-hosted workflow orchestration platform. Managing CI/CD pipelines usually involves jumping between different dashboards, hunting for specific process IDs, and digging through mountains of logs just to figure out why a build failed. This changes that by letting your agent do the heavy lifting for you. Instead of manual searching, you can just ask your agent to find the status of a specific project or tell it to pull the logs for a failed execution. It handles the navigation through your Concord instance, whether you need to see what's running right now or want to audit the structure of your entire organization. Because Vinkius makes it easy to connect these types of tools, you can keep your focus on fixing the actual problems rather than hunting for the data. Your agent becomes a direct line to your workflow orchestration, making it much faster to terminate stuck processes or check on new deployments. It's about getting the right information at the right time without the friction of multiple tabs. You can verify repository configurations or audit project scopes with a quick chat command, making your deployment cycle feel much faster.

## Tools

### list_running_processes
The list_running_processes tool lists all currently running processes in Concord. This gives you a high-level view of your current workload.

### terminate_process
The terminate_process tool stops a running process execution immediately. Use this to kill hung jobs or clear space in your queue.

### get_process
The get_process tool retrieves detailed info about a specific process execution. This gives you the full context of a single run.

### get_process_log
The get_process_log tool pulls the execution logs for a specific process. Use this to quickly see why a pipeline failed.

### start_process
The start_process tool triggers a new process execution in Concord. It lets you kick off workflows using natural language.

### list_repositories
The list_repositories tool gets a list of repositories configured for a project. This helps you see what code is tied to your workflows.

### get_project_details
The get_project_details tool retrieves detailed information about a specific project. Use this to understand project scoping and configuration.

### list_organizations
The list_organizations tool retrieves a list of all organizations in Concord. This helps you browse the overall structure of your instance.

### list_processes
The list_processes tool retrieves a list of process executions in Concord. Use this to see a history of what has run recently.

### list_projects
The list_projects tool retrieves a list of projects within an organization. This helps you navigate the hierarchy of your deployment environment.

## Prompt Examples

**Prompt:** 
```
Show me what's running right now.
```

**Response:** 
```
Here are the processes currently running in your Concord instance:

| Process ID | Name | Status | Runtime |
| :--- | :--- | :--- | :--- |
| `inst-8821` | **deploy-prod** | Running | 4m 12s |
| `inst-9902` | **unit-tests** | Running | 12m 05s |
| `inst-7731` | **db-migration** | Running | 1m 44s |

Would you like me to pull the logs for any of these?
```

**Prompt:** 
```
List all organizations available in my Concord instance.
```

**Response:** 
```
Your Concord instance contains the following organizations:

* **Engineering** (14 projects)
* **Data Platform** (6 projects)
* **QA Automation** (9 projects)
* **Security Ops** (2 projects)

Which organization would you like to explore further?
```

**Prompt:** 
```
Pull the logs for execution instance 'inst-58291'.
```

**Response:** 
```
Retrieving logs for `inst-58291`...

**Execution Status:** Failed
**Failed Task:** Run Integration Tests
**Error Context:** `ECONNREFUSED 127.0.0.1:5432` 

Would you like me to fetch the complete log output for this execution?
```

## Capabilities

### Stop running workflows
Use terminate_process to immediately kill a hung or stuck execution.

### Fetch execution logs
Pull the logs for a specific process using get_process_log to see why a build failed.

### View all active processes
See everything currently running in your instance with list_running_processes.

### Start new workflow executions
Trigger a new process execution in Concord using start_process.

### Browse project details
Retrieve full configuration data for a specific project with get_project_details.

### List all organizations
Browse the high-level structure of your instance with list_organizations.

### Retrieve repository lists
See which repositories are tied to your workflows using list_repositories.

## Use Cases

### Rapid incident response for failed builds
A build fails and the engineer needs the logs immediately. They ask the agent to pull the logs for a specific instance ID to see the error context.

### Clearing a blocked deployment queue
A process is hung and blocking the queue. The user tells the agent to stop the specific execution to free up resources.

### Auditing project structures
A new team needs to see what projects are available. The user asks the agent to list all projects within a specific organization.

### High-level workload monitoring
A manager wants to see what is running right now. The user asks the agent to show all active processes across the instance.

## Benefits

- Faster incident response by pulling logs for specific failed executions without switching tabs.
- Easier workload management by seeing all active processes in a single glance.
- Direct control over stuck jobs by killing hung executions instantly from your chat.
- Better visibility into your project scope and organization hierarchy for easier auditing.
- Reduced manual overhead by triggering new workflow executions using simple natural language.
- Quicker environment audits by retrieving full project configuration details on demand.

## How It Works

The bottom line is you get a conversational interface for your entire Concord CI/CD infrastructure.

1. Add the Concord MCP to your AI client and provide your instance URL and API token.
2. Ask your agent to perform a task, like listing all active processes or pulling logs.
3. Receive the status, logs, or project details directly in your chat.

## Frequently Asked Questions

**What can the Concord MCP do for my CI/CD?**
It gives your AI agent the ability to manage your Concord workflows. You can start processes, stop stuck jobs, and view your entire project structure through a chat interface.

**How do I use the Concord MCP to check logs?**
You can simply ask your agent to pull the logs for a specific execution. It will fetch the relevant log data and summarize the errors or status for you.

**Can I stop a stuck build using the Concord MCP?**
Yes, you can tell your agent to terminate a specific running process. It will immediately stop that execution in your Concord instance to clear up your queue.

**How does the Concord MCP help with auditing?**
It allows you to browse all organizations and project details across your instance. Your agent can quickly pull this information to help you audit your deployment environment.

**Can the Concord MCP list my organizations?**
Yes, your agent can retrieve a full list of all organizations configured in your Concord instance, showing you the high-level structure of your platform.

**Is the Concord MCP for self-hosted instances?**
Yes, it is designed to connect to your self-hosted Concord instance using your specific URL and API token, keeping your workflow data private.

**How do I create a Concord API token?**
You can create an API key via the Concord UI or by calling the `POST /api/v1/apikey` endpoint with your username and password.

**What is an instance ID in Concord?**
An instance ID is a unique identifier assigned to a specific execution of a process or flow. You use it to retrieve logs, check status, or terminate the execution.

**Can I stop a running process?**
Yes. Use the 'terminate_process' tool with the instance ID to stop a running execution at any time.