MCP connector · Developer

Pagerlane

Triage your Keep alerts and incidents by asking.

  • 14 tools
  • 69 tests passing
  • Free and open

InstallSupport the project

See it work

Example. A real tool and its real input. No live data is shown here.

You ask
“List my latest alerts.”
Your bot calls
keep_list_alerts with an optional limit
It gets back
Alerts from your own Keep server.

Install

The source for this connector is not public yet, so there is no command to copy.

Want early access or to help? Get in touch. General setup is in the Docs.

Facts

Tools
14
Tests
69 passing
Licence
Not stated yet
Source
Not public yet
Listing updated
31 October 2026
Maintained by
Bot Essentials

Tests were run on 27 October 2026 in a clean copy of each connector. You bring your own keys for any service it talks to.

Details and limits

Pagerlane is a local MCP server for Keep (keephq). The package name is pagerlane-mcp. You run it over stdio or Streamable HTTP. It does not start Keep for you, and it copies no Keep code.

Works with Keep (keephq). Not affiliated with or endorsed by Keep Alerting LTD.

Writes are confirm-gated. A write is a preview unless confirm:true. Omitted confirm does not call Keep.

Tools

  • keep_list_alerts

    List alerts

  • keep_search_alerts

    Search alerts with a CEL query

  • keep_get_alert

    One alert by fingerprint

  • keep_list_incidents

    List incidents

  • keep_get_incident

    One incident by id

  • keep_list_providers

    List providers, with credential fields removed

  • keep_list_workflows

    List workflows

  • keep_get_topology

    Service topology

  • keep_list_applications

    Applications taken from the topology

  • keep_acknowledge_alert

    Acknowledge an alert

  • keep_resolve_alert

    Resolve an alert

  • keep_enrich_alert

    Add string enrichments to an alert

  • keep_update_incident

    Change incident status, severity, or fields

  • keep_run_workflow

    Run a workflow