Integration

Coveralls integration

Coveralls API for code coverage tracking and reporting. Manage repositories, upload coverage reports from CI/CD pipelines, handle parallel build webhooks, and automate repository configuration. Integrates with GitHub, GitLab, Bitbucket, and other git providers.

Connect Coveralls How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Coveralls.Built from the 7 Coveralls tools below, on the connection you add once.

Common Coveralls use cases

parallel CI completion
CI/CD coverage reporting
displaying coverage data
automating repo onboarding
reprocessing failed builds
adjusting coverage thresholds
removing decommissioned repos
CI/CD pipeline setup
toggling PR comments
merging coverage reports

What you can do with Coveralls

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Repository, 4 operations

create_repositoryCreate repositoryPOSTCreates a new repository on Coveralls with coverage configuration settings.
delete_repositoryDelete repositoryDELETEDeletes a repository from Coveralls along with all its coverage data.
get_repositoryGet repositoryGETRetrieves configuration and metadata for a Coveralls repository including coverage settings, thresholds, and recent builds.
update_repositoryUpdate repositoryPUTUpdates coverage configuration settings for an existing Coveralls repository.

Build, 1 operation

rerun_buildRerun buildPOSTTriggers a rerun of a specific coverage build to reprocess its coverage data and update commit status.

Coverage, 1 operation

post_coveragePost coveragePOSTUploads coverage data to Coveralls from CI/CD pipelines as a JSON file via multipart form upload.

Webhook, 1 operation

webhook_parallel_doneWebhook parallel donePOSTSignals that all parallel CI jobs have completed and triggers final aggregate coverage calculation from combined reports.

Use Coveralls from Claude Code, Cursor or Codex

Connect Coveralls in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Coveralls operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Coveralls

Create your workspace
Sign up free. Nothing to install.
Connect Coveralls once
Add your Coveralls connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

Coveralls integration FAQ

What can you do with the Coveralls integration?

LiveContext exposes 7 operations on Coveralls, covering repository, build, coverage and webhook. Common uses include parallel CI completion, CI/CD coverage reporting and displaying coverage data.