Free setup on ROLLER Integration Packs until 31 August 2026. Use code ROLLER826. Check out ROLLER Integration Packs
← All connectors
CircleCI Partner Connector

Connect CircleCI Without Constraints

IntelliPaaS seamlessly connects CircleCI with your core business systems, enabling no-code integration for build visibility, failure triage and delivery reporting across cloud, on-prem and hybrid environments.

CircleCI's MCP offering moved during 2026: the original standalone package was archived and the server now exists in two supported forms — a hosted remote endpoint and a server built into the CircleCI CLI. Both are in preview, and CircleCI says the tool list should be expected to change. The hosted server is the safer of the two for most integrations: thirteen tools, all read except two, with a log tool that automatically reads the failed steps of a run. The CLI server exposes the whole CLI surface — config authoring and validation, org management, orbs, policies, runners and direct API access — which is substantially broader and more mutating. Authentication is OAuth2 or a personal API token, scoped to what that user can see, and on-premises CircleCI installs are reached by pointing at your own base URL.

CircleCI integration capabilities

  • List and read pipeline runs, workflows and jobs.
  • Read job logs, with failed steps surfaced automatically.
  • List build artifacts and job test results.
  • Download usage data for reporting, in ranges of up to 31 days.
  • Rerun a workflow, optionally only its failed jobs.
  • Cancel a running workflow.

These capabilities let build and test signal reach the systems that triage and report on delivery, without anyone opening the pipeline UI. IntelliPaaS handles field mapping, pagination and data type transformation automatically.

Common integration scenarios

  • Post failed job logs and likely causes into Slack or a pull request.
  • Raise a Jira or Linear issue automatically for a repeatedly failing test.
  • Rerun only the failed jobs of a flaky workflow under a controlled policy.
  • Alert PagerDuty when a production deployment pipeline fails.
  • Load build duration, success rate and usage data into Power BI or a warehouse.

These scenarios address the most common friction in continuous integration — failures triaged by hand, delivery metrics assembled from exports — by automating the flows between CircleCI and the platforms around it.

Deployment & security

Flexible deployment is essential for organisations operating in regulated industries or jurisdictions with strict data residency requirements. IntelliPaaS supports private cloud and on-premise deployments with full regional data sovereignty, and self-hosted CircleCI installs are reached by pointing at your own base URL rather than the hosted endpoint. All deployment modes receive the same feature set, connector library and support tier, with no capability trade-offs based on deployment choice.

Deployment mode
Data residency
Features
Best for
Cloud (SaaS)
Shared cloud
Full
SMB / mid-market, speed
Private Cloud
Customer VPC
Full
Regulated industries
On-Premise
Customer infra
Full
Data sovereignty, finance, healthcare
No capability trade-offs based on deployment choice.
GDPR-readyEncryption in transit and at restFull regional data residency

Why IntelliPaaS

  • No-code to pro-code flexibility for all integration needs.
  • End-to-end security with OAuth2 or per-user tokens scoped to that user's projects.
  • A narrow, mostly read-only hosted tool set, with the broader CLI surface available when needed.
  • Enterprise-grade observability with monitoring, alerting and audit logging.

Frequently connected apps

FAQ

Frequently asked questions

What authentication does the connector use?

OAuth2 or a CircleCI personal API token on the hosted server; the CLI server reuses credentials from a CLI login or a token environment variable. Scoping is whatever the user's project and organisation membership allows.

What can it change?

On the hosted server, only two things: rerunning a workflow, optionally failed jobs only, and cancelling one. Everything else is read. The CLI server exposes a much broader and more mutating surface, so we scope it separately.

How mature is it?

Both servers are in preview, and CircleCI says the available tools should be expected to change. Note that the older standalone npm package was archived in mid-2026 — configurations still referencing it should be migrated.

Can I deploy on-premise or in a private cloud?

Yes. Cloud (SaaS), private cloud in your own VPC, and fully on-premise or air-gapped deployments are all supported, and self-hosted CircleCI installs are reached through your own base URL.

Is my data secure?

Data is encrypted in transit and at rest, and IntelliPaaS is GDPR-ready. Access follows the connected user's projects, the hosted tool set is deliberately narrow, and on-prem modes keep build data inside your own infrastructure boundary.

Ready to connect CircleCI to your stack?

Our team will map your exact integration scenario, usually in a 30-minute session.