MCP Server

Ontime exposes an MCP server over Streamable HTTP.

What the MCP server does

The MCP server is guided to understand Ontime rundowns, so a connected agent can build and maintain them for you rather than just read data.
Point it at unstructured material — a pasted agenda, an email, a script, or a spreadsheet — and it will turn it into a clean, readable rundown, following Ontime's conventions for grouping, colours, cue naming and keeping tech detail in custom fields rather than titles.

From there the agent can edit, restructure and audit the rundown: creating and grouping events, filling custom fields, reordering entries, and flagging schedule gaps, overlaps or automation risks.

Note

The MCP server has no transport controls.
It can build and tidy your rundown but cannot start, stop or advance the timers, so it stays useful while planning without any risk to a live show.

TLDR: Connecting to MCP server step-by-step

Connecting to Ontime's MCP is just like any other server.
Your agent will be able to help you through the process if necessary.

1. In the editor page, navigate to Settings -> MCP Server
2. Copy the Client configuration snippet and add it to the agent settings along with the other MCP servers.
   If your server is behind a password, the link will contain a pre-signed token.

Quick check
The server should respond to MCP initialization requests at /mcp.
A plain browser GET request will return 405 Method not allowed, which is expected.

Endpoint

The default endpoint for connecting to the server is:

https://cloud.getontime.no/<stage>/mcp

while for local installs the default would be

http://localhost:4001/mcp

If Ontime is running on another host or port, replace localhost:4001 with that address.

Authentication

If Ontime has no session password configured, no MCP authentication is required.

If a session password is configured, authenticate with the hashed Ontime token. The settings UI generates an endpoint URL with the token in the query string:

http://localhost:4001/mcp?token=<hashed-token>

If your MCP client supports request headers, you can send the same token as a bearer token instead:

Authorization: Bearer <hashed-token>

This is the same token used in authenticated Ontime share URLs as the token query parameter. The raw session password is not accepted as the bearer token.

Client Configuration

Use a Streamable HTTP MCP client and point it at the MCP endpoint:

{
  "mcpServers": {
    "ontime": {
      "url": "http://localhost:4001/mcp?token=<hashed-token>"
    }
  }
}

Omit the token when Ontime is not password protected. If you prefer headers, use "url": "http://localhost:4001/mcp" and add an Authorization header with the same bearer token.