Repository navigation
Conversation
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>
This branch has not been deployed
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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.
connectors/checkly/): Checkly's hosted MCP server at one global endpoint. Customers connect with a Checkly service API key and their account ID.triggersholds 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.
Required before review
connectors/checkly/and nothing else is touched.checkly/engineering, reachable at thecontact_emailinconnector.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.
initializeWWW-Authenticatepointing at the protected resource metadataAuthorization: Bearer <service API key>andX-Checkly-Account, using a Read only service keytriggersvalues produce was answered with 200{"message": "Webhook received"}; the investigation opened and completed&in names, multi-line errors and a heartbeat monitor: valid JSON of the right types each timeconnector.yamlagainstconnectors/schema/v1/connector.schema.jsontests/test_connector_schema.py,tests/test_connectors_catalog.pyscan_aws_identifiers.pyon the added lineslogo-dark.svgNotes for reviewers:
{{NAME}}HTML-escapes the value and{{{NAME}}}does not, soRESULT_LINKuses three braces to keep the URL intact.Bearer {{{AWS_DEVOPS_AGENT_WEBHOOK_KEY}}}. With two braces a base64 key ending in=is escaped and the webhook answers 403.timestamp. Checkly'sSTARTED_ATis ISO 8601 for checks but not for heartbeat monitors, so the start time is indescriptioninstead.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
License confirmation
🤖 Generated with Claude Code