An astronaut overseeing a futuristic data hub
Download PDFMarkdown Version

Connect Coveralls Code Coverage Analytics API to your AI

Set it up once and it works in ChatGPT, Claude, Cursor, and any other client you love. It all runs safely in the background, so you can relax and focus on what really matters. Manage your testing metrics through natural conversation.

Ask AI about this Connector

Developed, maintained, and hosted by Vinkius.

MCP VERIFIED · PRODUCTION READY · VINKIUS GUARANTEED

Waiting for input…

Works with modern AI clients that support MCP, including ChatGPT, Claude, Cursor, and more.

ChatGPTClaudeCursorPerplexityGeminiMicrosoft CopilotRaycastMeta AI

Your AI does the work. We keep it safe and sound.

No other AI tool gives you this. Your workflow runs in the client you already love, your account stays protected, and you decide what the agent can and cannot do. It is the whole reason to make the switch.

Each Connector lives inside our infrastructure, the same place where your workflow runs. The three things below are already part of it, working quietly in the background so you never have to think about them. Nothing to add, nothing to set up, nothing to worry about.

A futuristic MCP client docking bay
V8 Isolate01

Each Connector runs inside its own sealed environment.

Each Connector runs inside its own sealed V8 runtime — no access to your files, your system, or other servers. A Connector never sees past its own request.

Kill Switch02

One switch stops every agent. Instantly.

One action deactivates every Connector, revokes every token, and ends every session at once. AI Governance keeps the record.

FinOps per User03

Spending limits that pause instead of surprise.

Every user keeps their own connections and credentials, isolated from everyone else. Anything that would cross your spending limit is held for your approval, not billed.

Three controls, built into the layer your AI connects through.

Curated set · 10 capabilities

We ship only the actions that matter.

Capability set01 / 03

01-04

4 capabilities in this set.

Part of 10 available through Coveralls.

  1. 01

    Get build web data

    Fetches the JSON representation of a specific build web page. This is useful for analyzing build details via your agent.

  2. 02

    Get file web data

    Retrieves JSON data for a specific source file web page. Use this to inspect file-level coverage directly.

  3. 03

    Close parallel build

    Closes a parallel build on Coveralls. This tells the system to finalize the build sequence.

  4. 04

    Create repo

    Creates a new repository on Coveralls. You'll need your personal API token to run this.

Capability set02 / 03

05-07

3 capabilities in this set.

Part of 10 available through Coveralls.

  1. 05

    Get job web data

    Gets the JSON data for a specific job web page. This provides deep insight into individual job execution.

  2. 06

    Get repo

    Retrieves information for a specific repository. It requires your personal API token for access.

  3. 07

    Get repo web data

    Fetches the JSON representation of a repository web page for quick data analysis.

Capability set03 / 03

08-10

3 capabilities in this set.

Part of 10 available through Coveralls.

  1. 08

    Rerun build

    Triggers a rerun of an existing build. Use this to resolve processing issues without manual intervention.

  2. 09

    Submit job

    Submits a coverage report to Coveralls. You provide the repo token, service details, source files, and git metadata.

  3. 10

    Update repo

    Updates the configuration of an existing repository on Coveralls using your personal API token.

Real work

What teams actually run

01

Automated Repo Setup

A DevOps engineer tells the agent to set up a new repository on Coveralls for a fresh project.

02

Debugging Coverage Failures

A developer triggers a build rerun when a transient CI issue causes a coverage report to fail.

03

Trend Analysis

A QA lead asks the agent to fetch web data to compare recent coverage trends against historical data.

04

CI/CD Integration

An agent submits a coverage job immediately after a test suite finishes in a CI pipeline.

Automate a task

Put Coveralls to work on one thing.

Step-by-step automations your AI runs through this Connector: the workflow, the prompts to start with, and the exact capabilities behind each move.

One connector, every AI

Coveralls works with the most popular AI clients.

These are the most popular clients, each with a step-by-step guide: one link, set up once, with governance and visibility built in. And because everything runs on the MCP standard, the same connection also works in any other compatible client — nothing to rebuild.

ClaudeClaudeChatGPTChatGPTGeminiGeminiPerplexityPerplexityGrokGrokMicrosoft CopilotMicrosoft CopilotCursorCursorVS CodeVS CodeWindsurfWindsurfJetBrainsJetBrainsClineClineLangChainLangChainVercel AI SDKVercel AI SDKLovableLovableZ.aiZ.aiRaycastRaycastQwen CodeQwen CodeKimi CodeKimi CodeLe ChatLe Chat

Building your own app? The connector is yours to use.

You don't need a client to put Coveralls to work: the same hosted connection plugs into your own applications and agent code, with the same governance on every request. Build with it, chat with it — one connection for both.

Observed, not estimated

961ms average. Fast in production.

Coveralls is checked daily against the live service.

Daily averagePeak 1171ms
Oct 3Today
Fastest day
810ms
Slowest day
1171ms
14-day trend
Slowing+5%

Connect your client

One URL. Every client.

Activate the Connector, copy your link, and paste it into the client you already use. 10 capabilities arrive ready to run.

Preview access · not provider authentication

The vk_preview_* token belongs to Vinkius preview infrastructure. It lets Claude discover and display the capabilities of Coveralls, so you can see the experience inside your AI.

It does not authenticate your account with Coveralls. Actions requiring credentials or live account data may not run until you activate the Connector and authorize the service.

Coveralls Connector

You're all set. Choose your MCP client and follow the setup instructions.

Connector linkhttps://edge.vinkius.com/vk_preview_4KFwfN2vWWEeowJibGZslVeROZZ50N2pFwaurAdx/mcp

Claude Desktop

Follow the steps below to connect in seconds.

  1. 1In Claude Desktop, open Settings → Connectors.
  2. 2Click “Add custom connector” and paste the connector link above as the remote MCP server URL.
  3. 3Click Add and start a new chat — Coveralls capabilities are ready to use.
Configuration · claude_desktop_config.jsonCopy
{
  "mcpServers": {
    "coveralls-code-coverage-analytics-api-mcp": {
      "url": "https://edge.vinkius.com/vk_preview_4KFwfN2vWWEeowJibGZslVeROZZ50N2pFwaurAdx/mcp"
    }
  }
}
  • Claude
  • ChatGPT
  • Cursor
  • VS Code
  • Windsurf
  • Claude Code
  • JetBrains
  • Cline

Step-by-step instructions for each client are in the guide. How to connect

Guided setup for Claude? Set up Coveralls in Claude and other AIs

See all the AI clients this connector works with ↑

Who it's for

Built for the work Coveralls owners hand off.

This MCP is built for engineering teams who need to keep testing metrics close to their coding environment.

  • 01

    DevOps Engineers

    Automate repository setup and monitor coverage trends across the whole organization.

  • 02

    Software Developers

    Check coverage status and submit reports without leaving the IDE.

  • 03

    QA Leads

    Analyze coverage regressions and manage build thresholds to ensure reliability.

FAQ

Questions Coveralls owners ask.

  • 01

    Which git providers are supported?

    This MCP works with repositories hosted on GitHub, GitLab, and Bitbucket.

  • 02

    Do I need a special token?

    Yes, you will need to provide your Coveralls Personal Access Token to manage repositories and access private data.

  • 03

    Can I use this with Cursor?

    Yes, this MCP is compatible with any MCP-compatible client, including Cursor, Claude, and Windsurf.

  • 04

    How do I fix a failed build processing?

    You can use the rerun_build capability to trigger a new processing attempt for a specific build.

  • 05

    Can the agent see my private repository data?

    The agent can access private repository data if you provide a personal API token with the necessary permissions.

  • 06

    How do I retrieve my repository's secret token for CI configuration?

    Use the get_repo capability 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.

  • 07

    Can I submit a coverage report for a specific CI job manually?

    Yes! The submit_job capability 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.

  • 08

    How do I finalize a parallel build once all individual jobs are finished?

    Use the close_parallel_build capability. 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.

Explore

More in Developer Tools

Suggestions

Connect Coveralls to Claude, Cursor, ChatGPT & more