Integration

Intuiface Web Triggers integration

Intuiface Web Triggers sends messages to running Intuiface experiences (kiosks, digital signage, interactive displays) that embed the Web Triggers interface asset, so an outside event can drive what the screen shows. List the experiences currently running and able to receive a message, and send a message with up to three extra values to all of them or only to those matching experience names or IDs, Player device names, Player IDs or Player tags. Only Premier and Enterprise Intuiface accounts can use it; Player and deployment management is the separate Intuiface Share and Deploy API. Authentication is an API key with the Web Triggers scope, created on the Credential Keys page of My Intuiface and sent in the x-api-key header.

Connect Intuiface Web Triggers How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

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

What you can do with Intuiface Web Triggers

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.

Available experience, 1 operation

list_running_experiencesList running experiencesGETLists the experiences currently running with the Web Triggers asset and able to receive a message, optionally filtered (all filters combine with AND), with the Player each runs on.

Send message, 1 operation

send_messageSend messagePOSTSends a message to the running experiences embedding the Web Triggers asset; with no filter it goes to ALL of them. Check status in the answer: sent, noConnectedExperience or noMatchingExperience.

Use Intuiface Web Triggers from Claude Code, Cursor or Codex

Connect Intuiface Web Triggers in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Intuiface Web Triggers 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 Intuiface Web Triggers

Create your workspace
Sign up free. Nothing to install.
Connect Intuiface Web Triggers once
Add your Intuiface Web Triggers 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.