# Coveralls MCP for AI Agents AI Agent Connect

> Coveralls lets your AI agent manage code coverage metrics and repository configurations. You can submit coverage reports, monitor build statuses, and manage parallel CI workflows directly through your favorite AI client.

## Overview
- **Category:** developer-tools
- **Price:** Free
- **Endpoint:** https://edge.vinkius.com/vk_preview_4KFwfN2vWWEeowJibGZslVeROZZ50N2pFwaurAdx/ai-agent-connect
- **Tags:** code-coverage, ci-cd, testing, quality-assurance, static-analysis

## Description

Imagine you're in the middle of a deployment and need to know if your latest push actually hit your coverage targets. Instead of switching tabs and hunting through a dashboard, you can just ask your agent. This Connector connects your Coveralls account to your workflow, letting you handle the heavy lifting of code quality tracking through plain text. You can set up new repositories, submit jobs with git metadata, or trigger a rerun on a failed build when a transient error messes things up. It handles the data heavy lifting for GitHub, GitLab, and Bitbucket integrations. If you're looking for a way to keep your CI/CD pipeline clean and your metrics accurate, Vinkius makes it easy to plug this into your existing setup. It's about getting the data you need without the clicking.

## Tools

### create_repo
Create a new repository on the Coveralls platform. This is useful for quickly spinning up new projects in your pipeline.

### get_build_web_data
Get the JSON representation of a build web page. Use this to pull specific build metrics into your chat.

### get_file_web_data
Get the JSON representation of a source file web page. It helps you see how specific files are performing.

### get_job_web_data
Get the JSON representation of a job web page. This provides deep insights into individual coverage jobs.

### get_repo
Get repository info from your Coveralls account. Use it to verify active status and retrieve tokens.

### get_repo_web_data
Get the JSON representation of a repo web page. This is great for summarizing high-level repository trends.

### rerun_build
Trigger a rerun of a build on Coveralls. It's a fast way to fix transient failures without manual clicking.

### submit_job
Submit a coverage report to Coveralls. It includes source files and git metadata for accurate tracking.

### update_repo
Update an existing repository on Coveralls. Use this to modify configurations on the fly.

### close_parallel_build
Close a parallel build on Coveralls. This helps manage complex CI workflows and aggregate data.

## Prompt Examples

**Prompt:** 
```
Is the coverage for the auth service above 90%?
```

**Response:** 
```
I've checked the latest coverage for the **auth service**. Here is the summary:

| Service | Coverage | Status |
| :--- | :--- | :--- |
| Auth Service | **92.5%** | ✅ Passed |

The coverage is currently tracking well above your 90% threshold.
```

**Prompt:** 
```
Rerun the last failed build.
```

**Response:** 
```
Triggering a rerun for the most recent failed build... 

**Success!** The request was successful, and Coveralls is now re-calculating the coverage data for that build. You can check the status again in a few moments.
```

**Prompt:** 
```
Give me the details for the main repo.
```

**Response:** 
```
I've retrieved the details for the **main repository**: 

*   **Status:** Active
*   **Repo Token:** `abc123xyz...` 
*   **Current Coverage:** 92.5%
*   **Provider:** GitHub
```

## Capabilities

### Create new repositories
Set up new project configurations on Coveralls automatically.

### Submit coverage reports
Send detailed job data including source files and git metadata to your account.

### Trigger build reruns
Restart build processing to resolve transient errors without manual intervention.

### Close parallel builds
Finalize aggregate calculations by closing out parallel CI sequences.

### Fetch repository metadata
Get JSON data for repository, build, and file pages to analyze trends.

### Update repository settings
Modify existing repository configurations and access tokens.

## Use Cases

### Verifying coverage on a specific file
A developer wants to see if a specific file hit the coverage target. They ask the agent to fetch the web data for that file to see the latest results.

### Automating bulk repository setup
A DevOps engineer needs to set up 10 new repositories. They ask the agent to create each one on Coveralls to avoid manual UI configuration.

### Fixing failed builds due to network blips
A build fails due to a transient error. The user asks the agent to rerun the build processing to get the coverage data updated.

### Checking repository status
A QA lead needs to see if a repository is active and what its current status is. They ask the agent to pull the repo info.

## Benefits

- Stop hunting through dashboards because you can pull repository info and build data directly into your chat.
- Fix transient build errors instantly by triggering a rerun of the build processing without leaving your IDE.
- Manage complex CI workflows by closing parallel build sequences to finalize aggregate calculations.
- Automate new project setups by creating repositories across GitHub, GitLab, and Bitbucket in seconds.
- Get instant data for your source files and build jobs to analyze coverage history and trends.
- Submit reports faster by sending coverage data and git metadata through a simple natural language command.

## How It Works

The bottom line is you get full control over your code coverage metrics without leaving your workspace.

1. Subscribe to the Coveralls MCP on Vinkius.
2. Provide your Coveralls Personal Access Token in your client configuration.
3. Ask your agent to check coverage, submit reports, or manage your repositories.

## Frequently Asked Questions

**Can the Coveralls MCP help with my CI/CD pipeline?**
Yes, it connects your agent to Coveralls to manage reports and monitor build statuses, making it easier to track code quality.

**How do I use the Coveralls MCP for my private repos?**
You'll need to provide your Coveralls Personal Access Token in the setup. This allows your agent to see and manage private repository data.

**Can I use this to manage GitHub and GitLab repos?**
Yes, it supports repository configurations for GitHub, GitLab, and Bitbucket, allowing you to manage all your projects in one place.

**What happens when I use the Coveralls MCP to rerun a build?**
The agent triggers a rerun of the build processing. This is great for resolving transient issues without you having to click through a dashboard.

**Can the Coveralls MCP submit coverage reports?**
Yes, it can submit detailed reports including source file data and git metadata directly to your Coveralls account.

**How does the Coveralls MCP handle parallel builds?**
It can trigger aggregate calculations and close parallel build sequences, which is helpful for managing complex CI workflows.

**How do I retrieve my repository's secret token for CI configuration?**
Use the `get_repo` tool by providing the service (e.g., 'github') and repository name. The agent will return the repository details, including the `repo_token` needed for your CI environment variables.

**Can I submit a coverage report for a specific CI job manually?**
Yes! The `submit_job` tool allows you to send coverage data directly. You'll need to provide the `repo_token`, `service_name`, `service_job_id`, and the `source_files` JSON array containing coverage metrics.

**How do I finalize a parallel build once all individual jobs are finished?**
Use the `close_parallel_build` tool. Provide your `repo_token` and the `build_num`. This triggers Coveralls to aggregate all parallel jobs and calculate the final coverage percentage for the build.