Kaltura MCP Server for Event Platform API

Overview

The Kaltura MCP Server for the Event Platform is a Model Context Protocol (MCP) implementation that exposes the Kaltura Event Platform API as a set of tools and resources consumable by AI assistants and developer tools. It translates high-level tool invocations into authenticated calls to Kaltura endpoints so agents can create, update, list and manage virtual events, sessions, templates and related metadata.

This server is useful when you want programmatic or assistive workflows around virtual events: for example, letting an assistant provision an event from a template, add sessions, adjust timezone-aware schedules, or enumerate existing events for reporting and automation. It is designed to run locally (or in a container) and be registered as an MCP provider with agents such as VS Code Copilot, Claude, or other MCP-capable tools.

Repository: https://github.com/kaltura/mcp-events

Features

• Create, update, and delete Kaltura virtual events
• Create and list event sessions and attach resources
• List and browse preset event templates and timezone metadata
• Pagination and filtering when listing events
• Configurable target Kaltura environment (NVP / EU / DE or custom URL)
• Exposes both “tools” (MCP tool actions) and “resources” (event objects) for assistants

Prerequisites

• Node.js 22 or newer
• Network access to the Kaltura Event Platform APIs
• A valid Kaltura Session (KS) that includes a user (used for authentication)

Installation / Configuration

Clone and install:

git clone https://github.com/kaltura/mcp-events.git
cd mcp-events
npm install

Build / run (local, example):

# build (if distributed source present)
npm run build

# run directly (dist/index.js expected)
node dist/index.js

Example mcp.json entry to register the server with an MCP-capable agent:

{
  "mcpServers": {
    "Kaltura Events API": {
      "transport": "stdio",
      "command": "node",
      "args": ["/home/you/mcp-events/dist/index.js"],
      "env": {
        "KALTURA_ENV": "NVP",
        "KALTURA_KS": "YOUR_USER_KS_HERE"
      }
    }
  }
}

Environment variables (examples):

Set these either in your shell, process manager, or in your agent’s mcp config.

Available Tools

The MCP server exposes a collection of tools (high-level actions) that agents can call. Typical tools include:

• create-event — Create a new virtual event with options (title, template, timezone, start/end)
• list-events — Return a paginated list of events with filters (status, date range)
• update-event — Modify an event’s properties (title, description, schedule)
• delete-event — Remove an event and its attached resources
• create-event-session — Add a session to an event (speaker, start/end, resources)
• list-event-sessions — List sessions for a given event id

Example JSON payload for create-event (tool input):

{
  "title": "Acme Product Launch",
  "templateId": "preset_123",
  "timezone": "Europe/Berlin",
  "startTime": "2026-06-15T09:00:00",
  "endTime": "2026-06-15T12:00:00",
  "metadata": { "department": "marketing" }
}

Available Resources

The server also surfaces read-only resource endpoints an assistant can reference:

• events — Detailed event objects (id, title, status, schedule, template)
• preset-templates — List of available templates (layout, defaults, placeholders)
• timezones — Supported timezone identifiers and offsets

Resources are modeled to be returned in a consistent JSON structure so agents can present or reason about them.

Use Cases

• Provision an event from a template:
  • Assistant calls create-event with a preset template and timezone, returns event id and join/config links.
• Add sessions to an existing event:
  • Use create-event-session to append speaker sessions with specific start/end times (timezones handled by server).
• Bulk listing and reporting:
  • list-events with date-range filters to create reports of upcoming or past events.
• Update schedule or cancel an event:
  • update-event to adjust times or delete-event to remove the event and its resources.
• Integrate with IDE assistants:
  • Register the server as an MCP provider (mcp.json) so code assistants can offer event-management actions inline.

Tips

• Ensure the Kaltura KS you provide includes a user context so actions are authorized.
• For non-default deployments, set KALTURA_PUBLIC_API to point at your region/IRP/FRP endpoint.
• Use pagination on list-events to avoid large result sets.

For more details, examples, and contribution guidelines, see the project source on GitHub: https://github.com/kaltura/mcp-events.