Integration

SIGNL4 integration

SIGNL4 delivers mobile alerts with tracked acknowledgement and escalation to an on-call team. This integration covers the team webhook: raise an alert with a title, a message and optional routing controls, and resolve an alert that was raised earlier with the same external id. The team secret is the credential and travels in the address, so there is no header or query key.

Connect SIGNL4 How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in SIGNL4.Built from the 2 SIGNL4 tools below, on the connection you add once.

Common SIGNL4 use cases

paging the on-duty engineer when a monitor fails
closing the alert automatically when a monitor recovers
raising an alert with a location for a field team
keeping SIGNL4 in sync with an external incident tracker

What you can do with SIGNL4

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

resolve_alertResolve alertPOSTResolves a SIGNL4 alert previously raised with a matching external id.
send_alertSend alertPOSTRaises a SIGNL4 alert that notifies the on-duty team members.

Use SIGNL4 from Claude Code, Cursor or Codex

Connect SIGNL4 in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its SIGNL4 operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect SIGNL4

Create your workspace
Sign up free. Nothing to install.
Connect SIGNL4 once
Add your SIGNL4 connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.

SIGNL4 integration FAQ

What can you do with the SIGNL4 integration?

LiveContext exposes 2 operations on SIGNL4, covering alert. Common uses include paging the on-duty engineer when a monitor fails, closing the alert automatically when a monitor recovers and raising an alert with a location for a field team.