MCP Event Intelligence MCP Server

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

claude mcp add event-intelligence -- npx -y mcp-event-intelligence

{
  "mcpServers": {
    "event-intelligence": {
      "args": [
        "-y",
        "mcp-event-intelligence"
      ],
      "command": "npx"
    }
  }
}

[mcp_servers.event-intelligence]
command = "npx"
args = ["-y", "mcp-event-intelligence"]

{
  "mcpServers": {
    "event-intelligence": {
      "args": [
        "-y",
        "mcp-event-intelligence"
      ],
      "command": "npx"
    }
  }
}

{
  "mcpServers": {
    "event-intelligence": {
      "args": [
        "-y",
        "mcp-event-intelligence"
      ],
      "command": "npx"
    }
  }
}

This one needs environment variables set before it will start: DATA_DIR (Persistent Event Intelligence state directory.), MCP_WRITE_ENABLED (Set to true to expose persistent trigger mutation tools. Read-only by default.), RUNTIME_WAKE_TARGETS_JSON (Optional operator-configured signed runtime wake targets.), TYPESAFE_API_KEY (Optional TypeSafe Jev API key for semantic-correlation triggers.), TYPESAFE_MODEL (Optional TypeSafe Jev model override. Defaults to jev-latest.). The author declared them in the registry entry; get the values from the project itself.