MCP connector · Developer
Pagerlane
Triage your Keep alerts and incidents by asking.
- 14 tools
- 69 tests passing
- Free and open
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_alertswith 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_alertsList alerts
keep_search_alertsSearch alerts with a CEL query
keep_get_alertOne alert by fingerprint
keep_list_incidentsList incidents
keep_get_incidentOne incident by id
keep_list_providersList providers, with credential fields removed
keep_list_workflowsList workflows
keep_get_topologyService topology
keep_list_applicationsApplications taken from the topology
keep_acknowledge_alertAcknowledge an alert
keep_resolve_alertResolve an alert
keep_enrich_alertAdd string enrichments to an alert
keep_update_incidentChange incident status, severity, or fields
keep_run_workflowRun a workflow