Get started with Jeero MCP for Timepad.ru

Use your Timepad.ru programme in ChatGPT, Claude or another compatible AI agent. Ask about upcoming events, explore the available ticket data and prepare work for your team.

You need an AI client that supports local MCP servers, a browser on the same computer as the MCP server, and access to the Timepad.ru connection details below. Jeero MCP works without WordPress.

1. Install Jeero MCP

If your agent can configure local MCP servers, give it this instruction:

Install and configure the local MCP server jeero-mcp using npx -y jeero-mcp. Then check that the Jeero tools are available.

You can also add the server using your client's MCP configuration:

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

The configuration location depends on your AI client. See the installation details on GitHub.

2. Create your Jeero connection

Create a Jeero connection for my venue. Ask me for its name. Select Timepad.ru using settings.theater = timepad_ru. Then call config_subscription to start private browser configuration. Do not ask for keys in chat or inspect or fill the configuration page.

Open the configuration link yourself and enter the separate access code. Depending on your app, Jeero may offer a URL prompt or return a link and code in chat. Enter all connection settings and keys in the private browser screen, then click Save and continue. If you need to select the ticketing platform there, save once to load its fields. Never paste keys into chat or let your agent inspect or fill this page.

The screen runs on 127.0.0.1 on the same computer as the MCP server. Links expire after 15 minutes or when the server stops. If your app's URL prompt does not work, ask your agent to call config_subscription with manual: true for a fresh link.

3. Connect Timepad.ru

Complete these fields yourself in the private configuration screen:

  • Timepad.ru API token (required).

Request a token here (http://dev.timepad.ru/api/oauth/). Make sure that the view_events option is checked.

  • Timepad.ru organisation ID (required).

You can find your organisation ID at the top of your Timepad.ru settings page.

Use the account whose events you want to import, then click Save and continue. Review any additional options shown in the screen; keep the defaults unless you need a narrower selection.

4. Ask your first question

Check my Timepad.ru connection with get_subscription and report whether its configuration is complete and how many connection errors it has. Then synchronise its events and report any synchronisation errors. Show next week's programme, start times and available ticket data, including the last successful synchronisation time. Use only this connection.

A complete configuration does not prove that your connection details are valid. Check the synchronisation result too.

Compare a few results with Timepad.ru: event names, dates, start times and ticket links where available. Missing ticket fields are not zero values, and availability alone does not show how many tickets were sold.

If no events appear, ask your agent to check this connection's safe summary from get_subscription, synchronisation status and logs. To correct settings, request a new link with config_subscription and make the changes yourself in the private screen. Synchronise again and check that upcoming events are available through the selected feed or account.

After connecting

Ask which events need attention, or prepare a mailing, social post or daily briefing. Your agent needs access to the relevant tools to apply website changes, send messages or schedule work. Sales trends and forecasts need suitable historical sales data.

Useful things to know

You can start for free with up to 10 upcoming events at any given time. See Jeero's plans and prices for a larger programme. Your AI client and additional tools may have their own costs and limits.

Jeero MCP synchronises through the Jeero service and stores an event cache on your computer. Data returned to your agent is handled by the AI service you choose. Additional tools have their own data settings.

These instructions use Jeero MCP 2.0.0 or later. Existing saved connections remain usable after updating. Only the ticketing-platform selection (settings.theater) can be supplied through the agent; all other connection settings go through the private screen. Subscription tools return safe summaries instead of saved values or configuration questions.

Need a hand with your connection? Email me.

Is your ticketing solution missing?

Please contact me so I can add your ticketing solution too.