Skip to content

feat(connectors): add Checkly connector - #263

Open
hlenke wants to merge 1 commit into
aws:mainfrom
hlenke:connectors/add-checkly
Open

hlenke wants to merge 1 commit into
aws:mainfrom
hlenke:connectors/add-checkly

Conversation

@hlenke

@hlenke hlenke commented Nov 16, 2026

Copy link
Copy Markdown

Description

Adds the Checkly connector, so DevOps Agent can read Checkly synthetic checks, uptime monitors, check results and root cause analyses during investigations, and so Checkly failure alerts can open investigations.

  • Connector (connectors/checkly/): Checkly's hosted MCP server at one global endpoint. Customers connect with a Checkly service API key and their account ID. triggers holds the values for a Checkly webhook alert channel.

This PR contains the connector only. It adds no skill.

Type of change

New partner connector. None of the boxes below names one, so they are left as they are.

  • New skill
  • New custom agent
  • New MCP server
  • Update to an existing skill, agent, or MCP server
  • Documentation or infrastructure change

Required before review

  • Repository layout is correct — the three files are in connectors/checkly/ and nothing else is touched.
  • A domain SME has reviewed and signed off. n/a: a connector is a definition, not a tool ("Partner Connectors" in CONTRIBUTING.md).
  • Evaluation evidence is included. n/a: this PR adds no skill.
  • No internal-only or proprietary content — no internal hostnames, account IDs, customer names, ticket numbers, internal URLs, or secrets in the tool, its examples, or its tests.
  • README is complete. n/a: the connector README is the customer setup guide the console renders, so it has setup steps and no sample prompt.
  • CHANGELOG updated and the version bumped. n/a: a new connector, starting at 1.0.0; connectors carry no changelog.
  • Named owner for ongoing maintenance — checkly/engineering, reachable at the contact_email in connector.yaml.

Testing

Tested against a non-production Agent Space in us-east-2, with Checkly registered as a custom MCP server using the same endpoint and headers this connector declares.

Check Result
Unauthenticated MCP initialize 401, with WWW-Authenticate pointing at the protected resource metadata
Registration with API key Succeeded with Authorization: Bearer <service API key> and X-Checkly-Account, using a Read only service key
Tool discovery 47 tools listed; the read-only ones were associated with the Agent Space
Tool calls The agent called Checkly tools in chat and in an investigation and returned correct check and result details
Trigger, end to end A Checkly webhook alert channel using the body these triggers values produce was answered with 200 {"message": "Webhook received"}; the investigation opened and completed
Trigger rendering The values were rendered with Handlebars against seven sample alerts, including quotes and & in names, multi-line errors and a heartbeat monitor: valid JSON of the right types each time
connector.yaml against connectors/schema/v1/connector.schema.json 0 errors
tests/test_connector_schema.py, tests/test_connectors_catalog.py 50 passed, 7 skipped (the skipped ones need mkdocs)
scan_aws_identifiers.py on the added lines 0 findings
Logo Square viewBox, 4,993 bytes, allowed elements only; rendered on light and dark backgrounds, so no logo-dark.svg

Notes for reviewers:

  • Template syntax. Checkly templates are Handlebars. {{NAME}} HTML-escapes the value and {{{NAME}}} does not, so RESULT_LINK uses three braces to keep the URL intact.
  • Webhook key. For the same reason the README tells customers to reference the webhook key as Bearer {{{AWS_DEVOPS_AGENT_WEBHOOK_KEY}}}. With two braces a base64 key ending in = is escaped and the webhook answers 403.
  • No timestamp. Checkly's STARTED_AT is ISO 8601 for checks but not for heartbeat monitors, so the start time is in description instead.
  • Recoveries. The README has customers send failures only.
  • Authentication. API key only for now. Checkly's authorization server does not offer dynamic client registration.

A Checkly trial account for your testing, the AWS account ID for the production allowlist, and security and support contacts are available on request. We will share them privately rather than in this description.

Connectors — complete if this PR adds or changes a connector

Security and safety

  • Read-only by default; any action that changes customer state is explicit, documented, and approval-gated. The README has customers create a Read only service key. Tools that change things need a key with a broader role, which the README describes as a separate, optional step.
  • Customer data stays in the customer's account. n/a: Checkly hosts the MCP server, and the agent reads the customer's Checkly data from it.
  • No destructive operations without an explicit, documented confirmation step. n/a: this PR adds a definition and no operations; which tools are enabled and which need approval is the customer's choice in DevOps Agent.

License confirmation

  • By submitting this pull request, I confirm that my contribution is made under the terms of the Apache License 2.0.

🤖 Generated with Claude Code

Adds connectors/checkly: the definition of Checkly's hosted MCP server
(API-key auth with a service API key and account ID), webhook trigger
values for Checkly alert channels, the setup guide and the logo.

Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
@hlenke
hlenke requested a review from yeremyjt as a code owner November 16, 2026 22:32

This branch has not been deployed

No deployments
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant