Be the first to get access to new connectors. Get early access →
ConnectorBay Early access

Coralogix (BYOK) — connector documentation

  • MCP endpoint: https://byok-coralogix-data-pipeline.connectorbay.com/mcp
  • REST API: POST https://byok-coralogix-data-pipeline.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://byok-coralogix-data-pipeline.connectorbay.com/openapi.json
  • Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
  • Authentication: your own Coralogix Coralogix API key with read permissions for the data pipeline objects, sent in the X-Upstream-Key header of every request (never stored, logged or cached)
  • Health: https://byok-coralogix-data-pipeline.connectorbay.com/health · Tool schemas: https://byok-coralogix-data-pipeline.connectorbay.com/tools.json
  • Publisher: Unify Dynamics LLC · connectorbay.com/byok-coralogix-data-pipeline · agent@connectorbay.com

What Coralogix (BYOK) is for

Coralogix (BYOK) lets an AI assistant read your own Coralogix data through the Coralogix API with a key you supply (Coralogix API key with read permissions for the data pipeline objects). Read-only: 12 tools (list_events2metrics, get_events2metrics, get_events2metrics_limits, list_rule_groups, get_rule_group, list_retention_tags, list_quota_policies, list_enrichments, list_custom_enrichments, get_logs_archive_target, get_metrics_storage_config, list_recording_rule_sets). The BYOK key travels with each request, is used for that one call only and is never stored, logged or cached; it is only ever sent to api.eu1.coralogix.com, api.eu2.coralogix.com, api.us1.coralogix.com, api.us2.coralogix.com, api.us3.coralogix.com, api.ap1.coralogix.com, api.ap2.coralogix.com, api.ap3.coralogix.com. Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Coralogix. Coralogix and its logos are trademarks of their owners and are used only to say which service the connector works with.

Ask your assistant things like:

  • "Which logs-to-metrics rules are configured in Coralogix?"
  • "Show the details of one Coralogix events-to-metrics rule"
  • "How close am I to my Coralogix logs-to-metrics limits?"
  • "Which parsing rule groups does my Coralogix team have, in what order?"
  • "Show one Coralogix parsing rule group"
  • "Which retention tags are defined in Coralogix?"

What it does

  • list_events2metrics: List the team's events-to-metrics rules (logs or spans turned into metrics) with type, data source and permutation limits.
  • get_events2metrics: Get one events-to-metrics rule by id: name, description, type, data source and permutation limit state.
  • get_events2metrics_limits: Show how many events-to-metrics rules, label permutations and labels the team may use and how many are used.
  • list_rule_groups: List the log parsing rule groups with name, order, enabled flag, creator and description (matchers and subgroups are not returned).
  • get_rule_group: Get one parsing rule group by id with its name, order, enabled flag and creator.
  • list_retention_tags: List the retention tags (named data retention periods) available to the team with their order and whether they can be edited.
  • list_quota_policies: List the data plan policies that decide priority and retention per application or subsystem, with order, priority and enabled state.
  • list_enrichments: List the enrichment rules that add geo, suspicious-IP or similar fields to incoming logs, with source field and target field names.
  • list_custom_enrichments: List the custom enrichment lookup files with name, description, file size and version (file contents are not returned).
  • get_logs_archive_target: Show where logs are archived: S3 bucket and region or IBM COS endpoint, archive format and whether archiving is active.
  • get_metrics_storage_config: Show the metrics archive configuration: bucket, prefix, whether it is disabled and retention days per resolution.
  • list_recording_rule_sets: List the Prometheus-style recording rule sets with id and name (rule groups inside are not returned).

BYOK key

You bring your own Coralogix Coralogix API key with read permissions for the data pipeline objects (https://coralogix.com/docs/user-guides/account-management/api-keys/api-keys/). Your assistant sends it in the X-Upstream-Key header with each request. ConnectorBay uses it for that one call only: it is never stored, logged or cached, never shown in an answer, and it is only sent to api.eu1.coralogix.com, api.eu2.coralogix.com, api.us1.coralogix.com, api.us2.coralogix.com, api.us3.coralogix.com, api.ap1.coralogix.com, api.ap2.coralogix.com, api.ap3.coralogix.com over https, with no redirects followed. Create a key with the fewest permissions the tools need (read-only if the provider offers it), and revoke it at the provider whenever you like.

Data sources

Live from the Coralogix API (api.eu1.coralogix.com, api.eu2.coralogix.com, api.us1.coralogix.com, api.us2.coralogix.com, api.us3.coralogix.com, api.ap1.coralogix.com, api.ap2.coralogix.com, api.ap3.coralogix.com) with a BYOK key; documentation: https://coralogix.com/docs/api-reference/. Endpoints checked against that documentation on 2026-10-16.

What it is not

Unofficial connector by Unify Dynamics LLC: not affiliated with, endorsed by or sponsored by Coralogix. Coralogix and its logos are trademarks of their owners and are used only to say which service the connector works with. It is read-only: it never creates, changes, sends or deletes anything in your Coralogix account.

Built for: Worldwide. Languages: English.