CI/CD plugins · MCP server

Enterprise CI/CD integrations for API testing

Six first-party CI/CD plugins (Jenkins, GitHub Actions, Azure DevOps, GitLab CI, CircleCI, Bitbucket Pipelines) plus a native MCP server for Claude Desktop, Cursor, and any MCP-compatible AI agent. Quality gates, audit-ready JUnit/JSON artifacts, on-prem and air-gapped support.

Book DemoSee pricing

Why integrate Shift-Left API with your pipeline?

Move API quality checks earlier in your delivery process. Catch failures before they merge — automatically.

Quality gates in every build

Set pass-rate thresholds and error-test policies so broken APIs never reach production. Gate results map directly to your pipeline step status.

XML & JSON artifacts

Publish XML for native test-result tabs and JSON summaries for custom reporting — all written to your workspace automatically.

Zero-friction setup

Install the plugin, add your credentials, and start testing. No custom scripts, no CLI dependencies, no learning curve.

GitHub Repository

All integrations in one place

Browse all six CI/CD plugin packages and the MCP server at Total-Shift-Left/Shift-Left-API-Integrations. Download the latest builds (HPI, VSIX, Docker, npm, GitHub Action), review changelogs, and open issues or feature requests.

View on GitHub

Available integrations

Six first-party CI/CD plugins plus a native MCP server — production-ready and installable today.

Jenkins

Available

Add Shift-Left API into Jenkins Freestyle jobs with minimal setup.

  • Build step for Freestyle projects with full UI configuration
  • One-click Test Connection to verify credentials
  • Configurable quality gate with pass threshold and error-test checks
  • XML and JSON summary workspace artifacts
  • Build sidebar link with execution summary
View integration details

GitHub Actions

Available

First-party GitHub Action with quality gates and JUnit/JSON artifacts.

  • GitHub Action installs in two lines of YAML
  • Quality gates exit non-zero to block PR merges via branch protection
  • JUnit XML pairs with dorny/test-reporter for inline PR test summaries
  • Matrix-friendly for parallel test pack execution
  • Self-hosted runner support for air-gapped Shift-Left deployments
View integration details

Azure DevOps

Available

Run Shift-Left API test packs directly inside Azure Pipelines.

  • Trigger test run packs via the ShiftLeft public API
  • Quality gates with configurable pass thresholds
  • XML and JSON summary artifact output
  • Output variables for downstream pipeline steps
  • Multi-tenant support with optional Tenant ID
View integration details

GitLab CI

Available

Docker image and CLI for any GitLab Runner — cloud or self-managed.

  • Native JUnit reporting in GitLab pipeline and merge request UI
  • Protected, masked CI/CD variables for credential safety
  • parallel:matrix support for multi-pack runs
  • Works with self-managed GitLab + self-hosted Shift-Left in air-gapped environments
  • Quality gate integrates with "Pipelines must succeed" merge check
View integration details

CircleCI

Available

CLI for any CircleCI job; orb-compatible config pattern.

  • JUnit results render natively in CircleCI Tests tab
  • CircleCI Context-secured credentials for org-wide scoping
  • Self-hosted runner support for firewalled Shift-Left deployments
  • Parallelism via shards or independent jobs
  • Workflow approval gates downstream of test results
View integration details

Bitbucket Pipelines

Available

Bitbucket Pipe and Docker image for Bitbucket Cloud Pipelines.

  • Both pipe: shorthand and docker run forms supported
  • Workspace and repository variables for credential scoping
  • Branch protection via "Require successful builds" merge check
  • Self-hosted runner support for air-gapped environments
  • Parallel steps for matrix execution
View integration details

MCP Server (Claude, Cursor, AI Agents)

Available

Native Model Context Protocol server — drive testing from your AI agent.

  • Six tools: generateTests, enrichTest, explainCoverage, generateForGaps, analyzeEndpoint, validateTests
  • Four resources: test://coverage, test://gaps, test://schema, test://output
  • Works with Claude Desktop, Cursor, Continue, and any MCP client
  • No legacy enterprise platform (ReadyAPI, Tosca, Parasoft) ships an MCP server today
  • stdio transport keeps credentials local in environment variables
View integration details

Public REST API

No native plugin? Use the REST API from any CI/CD tool

Every Shift-Left API action the plugins perform is available as a public REST endpoint. If your pipeline can make an HTTP call, it can trigger test packs, apply quality gates, and fetch results — GitHub Actions, GitLab CI, CircleCI, Bitbucket Pipelines, Bamboo, TeamCity, AWS CodeBuild, or any custom runner.

  • Authenticate with email and password to obtain a bearer token
  • Trigger a test run pack and receive an execution ID
  • Poll execution status and retrieve full results
  • Download XML and JSON summary artifacts for your pipeline
  • Apply your own quality gate logic with pass-rate thresholds
View API referenceRequest an integration
trigger-test-pack.sh
# 1. Login and grab the bearer token
TOKEN=$(curl -s -X POST \
  "$SHIFTLEFT_URL/api/v1/auth/login" \
  -H "Content-Type: application/json" \
  -d '{"email":"'"$EMAIL"'","password":"'"$PWD"'"}' \
  | jq -r .token)

# 2. Trigger a test run pack
EXEC_ID=$(curl -s -X POST \
  "$SHIFTLEFT_URL/api/v1/test-packs/$PACK_ID/run" \
  -H "Authorization: Bearer $TOKEN" \
  | jq -r .executionId)

# 3. Poll for completion and fetch results
curl -s \
  "$SHIFTLEFT_URL/api/v1/executions/$EXEC_ID" \
  -H "Authorization: Bearer $TOKEN"

Get started in three steps

1

Install the plugin

VSIX (Azure DevOps), HPI (Jenkins), GitHub Action, Docker image (GitLab/Bitbucket), or npm CLI (CircleCI). One-time setup per CI tool.

2

Configure credentials

Add your Shift-Left API email and password as scoped secrets — protected GitHub Secrets, GitLab CI/CD variables, CircleCI Contexts, or Bitbucket secured variables.

3

Run in your pipeline

Add the build step or job, pick a test pack, set your quality gate, and let CI handle the rest. Each plugin emits JUnit XML and JSON artifacts.

Integration FAQs

Contact us at

support@totalshiftleft.com

to learn more

  • Which CI/CD integrations does Total Shift Left support?
    Six first-party plugins: Jenkins (Java/Maven HPI), GitHub Actions, Azure DevOps (VSTS task), GitLab CI (Docker), CircleCI (CLI), and Bitbucket Pipelines (Pipe + Docker). Plus a native MCP server for Claude Desktop, Cursor, and any MCP-compatible AI agent. Each integrates the test run lifecycle (trigger, poll, JUnit/JSON artifact), supports quality gates, and is published as a vendor-native artifact — not a generic webhook wrapper.
  • Do I need a Shift-Left API account to use the plugins?
    Yes. The plugins authenticate against your Shift-Left API instance using the public REST API. You need a user account with permission to call the CI/CD API endpoints. For production use, create a dedicated service account with project-scoped permissions.
  • Can I run tests against private or internal APIs?
    Yes. As long as the CI/CD agent or runner has network access to your Shift-Left API server URL, tests will execute normally. For self-hosted Shift-Left deployments behind a corporate firewall, run the CI/CD job on a self-hosted runner inside the same network. The same pattern applies to all six CI/CD plugins.
  • What happens when a quality gate fails?
    You control the outcome. Each plugin exposes a pass-rate threshold and an ERROR-test policy — either failing causes the pipeline step to exit non-zero, which fails the job. Combine with branch protection rules in your VCS to block PR/MR merges on quality regressions. The gate decision is also available as an output variable for downstream logic.
  • What is the MCP server, and why does it matter?
    The Model Context Protocol is an open standard introduced by Anthropic in late 2024 that lets AI agents drive external systems through a tool/resource interface. Total Shift Left ships a native MCP server so Claude Desktop, Cursor, and other MCP-compatible agents can drive test generation, coverage analysis, and execution from inside the conversation. None of the legacy enterprise platforms (ReadyAPI, Tricentis Tosca, Parasoft SOAtest) currently ship an MCP server.
  • Is there a cost for the CI/CD plugins and MCP server?
    The plugins and MCP server are free to install. You need an active Shift-Left API subscription to run tests. The MCP server is gated to Trial, Professional, and Enterprise tiers; Citizen Developer (free forever, single seat) does not include MCP access. See the pricing comparison for the full feature matrix.
  • Can I use Shift-Left from a CI/CD tool that's not on the list?
    Yes. Every action the plugins perform is available via the public /api/v1 REST API. Bamboo, TeamCity, AWS CodeBuild, Buildkite, Drone, custom runners — anything that can make HTTP calls can trigger test packs, apply quality gates, and fetch results. See the public REST API section below for code examples.

Ready to automate API testing in your pipeline?

Start your free 15-day trial. Install a plugin and run your first test pack in minutes.

Start TrialBook Demo