Check your app

Start with one URL. Get a report on your computer, in CI, or through your AI assistant.

Download configuration to start

Configuration preview

Keep an existing config and merge these settings. Tokens stay in your environment or CI secret store.

Run your first check

Put the downloaded file in your project folder, then run:

Open the HTML report at the path printed after the check (report:). Need help? comber doctor in the updated CLI names what is missing.

Add a CI check

Commit the downloaded configuration. Add the same browser-install and check commands to your pipeline. Store connector credentials as CI secrets; supply the commit SHA at run time.

Open CI adapters

Configuration is prepared locally. No repository or pipeline has been changed.

Use your AI assistant

No Comber dashboard token is required. Findings return to your AI client; MCP does not publish reports to this dashboard. Access to your AI client is separate. Client attachment is not verified here.

Your AI client

Add this stdio entry to an AI client that accepts an mcpServers JSON configuration. Keep existing entries. Restart the client, then confirm Comber appears in its tool list.

1. Install the matching browser

npx -y [email protected] install-browsers

2. Check existing entries

codex mcp list

If comber already exists, inspect and reuse it. Do not run the add command over an existing entry.

3. Add Comber if it is missing

Preview the command below before running it. It adds a local Comber entry to your Codex configuration. Codex launches the pinned package through npx when it connects. Copying changes nothing. Keep an existing entry; skip this step if Comber is already registered.

codex mcp add comber -- npx -y [email protected] mcp

4. Check tools in Codex

Open a fresh Codex session and confirm comber_scan appears in its MCP tools. A saved entry alone does not verify a connection.

Instructions prepared — commands are ready to copy.
Tools visible in Codex: verify in your client.
Scan result returned: verify in your client.

Need help connecting?

Codex or npm is missing. Install the Codex CLI and a supported Node.js version that includes npm. Reopen your terminal, then try the commands again.

Browser is missing. Run the matching browser-install command above on the computer that runs Comber, then retry.

Comber tools are missing. Check existing entries with the inspection command above. Open a fresh Codex session and review its MCP startup error. Keep existing configuration while you investigate.

The scan failed. Read the tool error in Codex. Check the app URL and that the app is reachable from your computer. For a private app you own, enable the private-app option above and copy a fresh request. A failed request does not verify a scan.

Remove an entry you just added

Only remove comber if you added it for this setup. Keep any entry that existed before.

codex mcp remove comber

Request your first scan

Connector credentials

Set these environment variables on the computer or CI runner that runs Comber:

Comber does not collect these credentials here. Required values being present does not prove delivery.

Connector marketplace

Choose a destination above to generate its configuration. Explore the available connectors below.

Webhookwebhook

Webhook

webhook

POST the redacted run record (JSON) to any URL, with an optional bearer token.

Required env

COMBER_WEBHOOK_URLCOMBER_WEBHOOK_TOKEN

Config snippet

{"use":"webhook","on":"fail"}

Set up Webhook

Slacknotifier

Slack

notifier

Post a run summary to a Slack channel via an Incoming Webhook.

Required env

COMBER_SLACK_WEBHOOK_URL

Config snippet

{"use":"slack","on":"fail"}

Set up Slack

Discordnotifier

Discord

notifier

Post a run summary to a Discord channel via a webhook.

Required env

COMBER_DISCORD_WEBHOOK_URL

Config snippet

{"use":"discord","on":"fail"}

Set up Discord

GitHub commit statusreport

GitHub commit status

report

Set a pass/fail commit status on the checked SHA (shows as a PR check).

Required env

GITHUB_TOKENGITHUB_REPOSITORYGITHUB_SHAGITHUB_API_URL

Config snippet

{"use":"github","on":"fail"}

Set up GitHub commit status

GitLab commit statusreport

GitLab commit status

report

Set a pass/fail commit status on the checked SHA (shows on the MR).

Required env

GITLAB_TOKENGITLAB_PROJECT_IDGITLAB_COMMIT_SHAGITLAB_API_URL

Config snippet

{"use":"gitlab","on":"fail"}

Set up GitLab commit status

Bitbucket build statusreport

Bitbucket build status

report

Set a pass/fail build status on the checked commit (shows on the PR).

Required env

BITBUCKET_TOKENBITBUCKET_WORKSPACEBITBUCKET_REPO_SLUGBITBUCKET_COMMIT

Config snippet

{"use":"bitbucket","on":"fail"}

Set up Bitbucket build status

JUnit reportreport

JUnit report

report

Write findings as a JUnit XML report any CI test-summary UI can render.

Required env

None — no secrets required.

Config snippet

{"use":"junit","on":"fail"}

Set up JUnit report

Linearissue-tracker

Linear

issue-tracker

File a Linear issue for a run with failures.

Required env

COMBER_LINEAR_API_KEY

Config snippet

{"use":"linear","on":"fail"}

Set up Linear

Jiraissue-tracker

Jira

issue-tracker

File a Jira issue for a run with failures.

Required env

JIRA_BASE_URLJIRA_EMAILJIRA_API_TOKEN

Config snippet

{"use":"jira","on":"fail"}

Set up Jira

Microsoft Teamsnotifier

Microsoft Teams

notifier

Post a run summary to a Teams channel via an Incoming Webhook.

Required env

COMBER_TEAMS_WEBHOOK_URL

Config snippet

{"use":"teams","on":"fail"}

Set up Microsoft Teams

Azure DevOps statusreport

Azure DevOps status

report

Set a pass/fail commit status on the checked commit (shows on the PR).

Required env

AZURE_DEVOPS_TOKENAZURE_DEVOPS_ORG_URLAZURE_DEVOPS_PROJECTAZURE_DEVOPS_REPO_IDAZURE_DEVOPS_COMMIT

Config snippet

{"use":"azure-devops","on":"fail"}

Set up Azure DevOps status