Integration · Automate and collaborate

CircleCI and Meteor AI agents

Connect CircleCI to an internal Met: check runs, failed jobs, logs and failing tests, and rerun a workflow if the admin allows it.

Book a demo See every integration

How does CircleCI connect to Meteor?

With the CircleCI ready connector, your Met uses CircleCI's hosted MCP server with the account the admin authorizes, and it gets 9 tools. It lists a project's runs or your own, filtered by branch or status, opens a run with its outcome and config errors, brings a job step by step, reads the logs of the failed steps and lists the tests that did not pass. It also exports the organization's usage data. Rerunning a workflow, from the start or only from what failed, and canceling a running one start turned off until the admin turns them on.

What it automates

What a Meteor Met does with CircleCI

Tell you why the last run failed

When someone asks on WhatsApp why the change did not ship, the Met lists the branch's runs, opens the latest one and tells you whether it failed and whether there were config errors.

Read a job's error

With the failed job's ID, the Met brings its steps with their exit codes, reads the logs of the failed steps and lists the tests that did not pass.

Rerun only what failed

If the admin turned on the retry action, which starts turned off, and you ask it to retry a workflow by its ID, the Met reruns it only from the failed jobs, reusing the ones that already passed.

9 tools

Everything your Met can ask CircleCI for

Each one is a real action in the connector. You can switch off the ones you would rather it never used.

Tool	What it does
`list_runs`	Lists a project's runs, or your own across all projects, with filters by branch or status.
`get_run`	Returns a run with its phase, outcome, repository details and config errors.
`get_workflow`	Returns a workflow with its name, phase and outcome.
`rerun_workflow`	Reruns a workflow from the start, or only the failed jobs and everything downstream of them. Starts turned off.
`cancel_workflow`	Cancels a running workflow. Starts turned off.
`get_job`	Returns a job with its phase, outcome and per-step detail, including each step's exit code.
`get_job_logs`	Returns the output of a job's steps; if no step is named, it reads the failed ones.
`list_job_tests`	Lists a job's test results; by default only the failing tests.
`download_usage_data`	Exports an organization's usage data as CSV files, for a range of up to 31 days.

The limits

What the CircleCI integration does NOT do

We would rather say it here than have you find out during rollout.

It does not ask you for confirmation in the chat before rerunning a workflow. Retrying and canceling start turned off; if the admin turns them on in Connections, the Met runs them, and they change the real state of your CI.
It does not write or fix your code. The Met reads the failures and tells you about them; the fix is your team's.
It does not edit CircleCI configuration or manage orbs. CircleCI recommends its command line MCP for those tasks.
It does not pay your CircleCI plan. Usage runs on your CircleCI account; Meteor does not resell the service.

Before you start

What you need to connect CircleCI

1

A CircleCI account with access to the projects

The account your team signs in to CircleCI with. The Met sees the projects that account can access.
2

Connect it in Met

In Met, open Connections → CircleCI → Connect. A CircleCI window opens so you sign in and authorize Met. Then you choose which actions stay on.