AI assistant and MCP server: connecting to the app

The app can work together with an AI assistant. The assistant opens the same window you see. It reads projects and settings, presses the same buttons and starts the work. All of this happens on your screen, and you can step in by hand at any moment. You set the assistant's rights, and by default that is read-only.

What this gives you

Before, everything in the app was done by hand. Now you can name a task in words:

• "show me what projects I have";
• "raise the contrast and put the watermark in the bottom right corner";
• "set up forty sources from this file";
• "start the work and tell me when it finishes";
• "why was nothing created".

The assistant sees the same settings, the same labels and the same progress as you. There is no separate mode without a window: the window stays open on the screen the whole time.

What the assistant cannot do:

• work with Windows' own file and folder picker windows, the path is typed there as text;
• close system windows for you;
• change its own access level.

Default rights are read-only

The default access level is "Read only". The connection by itself changes nothing and starts nothing. Until you raise the level, the assistant only reads.

What it can access:

• the list of projects and the settings of each of them;
• the contents of lists and tables;
• the window open on the screen right now;
• the plan and progress of video creation, the row-by-row result;
• the wallet operation history and the download history;
• source check progress and app statistics;
• the tail of the log and a picture snapshot of the window.

What it is not allowed to do:

• any change to settings and any clicks;
• starting a preview or video creation;
• stopping the work;
• closing tabs and the app;
• activating a key;
• any deletions.

Five access levels

Level	What it adds	Actions available
"Read only"	"The assistant sees projects, settings and their structure, but changes and starts nothing."	34
"Reading and edits in the interface"	"Plus changing settings: sliders, text, watermarks, placement in the template, renaming projects."	57
"Edits and previews"	"Plus starting previews. A preview is created on the device and does not spend the balance. If a daily video limit applies, each preview uses one video from it."	60
"Full, without deletion"	"Full working access: starting video creation. Video creation in the cloud spends the balance. Plus closing tabs and the app. WITHOUT deleting projects or clearing lists."	69
"Full, with deletion"	"Everything above plus irreversible deletions: deleting projects and clearing lists."	75

The levels go up step by step: each new level includes everything from the previous one. The level is chosen in the "Assistant access level" list. The choice is written right away. The window itself says so too: "The choice is saved right away, no separate saving needed."

A new level applies to the next connection. Changing the level during a session changes nothing. Disconnect the assistant and connect again.

How to turn it on and connect

1. Click the menu button in the header of the main window. It is an icon of three bars with no label.
2. Choose the "Global integrations" item.
3. In the "MCP server" card, click "Open".
4. In the "Assistant access level" list, choose the level you need.
5. Click "Create .mcpb file". The line File created: <full path> appears below.
6. Click "Show in folder". The button becomes available after a successful build.
7. Double-click the VUB.mcpb file to add it to Claude Desktop.

The card is labeled: "Access for an AI assistant (Claude Desktop, for example) to the app". Above the build button there is an explanation: "Create the VUB.mcpb file - the path to the app will be written for this device. Then add this file to your assistant."

Another assistant

For Codex, Cursor and others there is a fallback. Expand the "Another assistant (Codex, Cursor)" row, it has a triangle in front of it. Inside is ready-made text and the "Copy config" button. The row is at the very bottom of the "MCP server" window: you need to scroll down to it with the mouse wheel.

The whole path to the "Another assistant (Codex, Cursor)" row: from the menu button in the header to the expanded block with ready-made text.

Copy the text and send it to your assistant. It will then explain how to add the connection. The first line of this text is a ready-made request to it: "Please tell me how to install this MCP server into you, or install it yourself."

The explanation in the window reads: "For another assistant (Codex, Cursor) or a manual setup: copy the config and send it to the assistant - it will tell you how to add the server."

What is needed on the assistant's side

• The assistant must be able to add such connections. For Claude Desktop it is the VUB.mcpb file, for the others - the text from the "Another assistant (Codex, Cursor)" block.
• The assistant must run with administrator rights. The app really needs these rights. Without them the start fails even before the window appears.
• The app must already be activated through a normal start. Under the assistant's control the activation window is not shown.
• The VUB.mcpb file is built on this device and fits only this device. The path to the app is written inside.

Neither a port nor a separate password is needed for this connection. The app key is never handed to the assistant, whatever happens.

Rules for working together

• The app runs exactly as long as the assistant's session lasts. When the session ends, the app closes.
• A second instance will not start. If you already have the app open, a start from the assistant is rejected.
• While the assistant has a modal window open, you are locked out, not the assistant. The mouse and keyboard do not work at that time, while the assistant's clicks go through. The app sends the assistant a separate warning about this.
• One action has a 20-second time limit. When it runs out, the assistant gets a refusal, but the action itself keeps running. It must not be repeated blindly, especially where money is spent.
• A file the assistant exports is not written over an existing one.
• When sources are exported, the login and password in the proxy address are covered with a marker. Make a full copy for importing back yourself with the button in the "Sources" section.
• After reinstalling or moving the app, build the VUB.mcpb file again.

Refusals and what to do

Text	What to do
"Could not create VUB.mcpb. Check the write permissions for the app data folder."	Check that the app data folder is writable and click the button again

The assistant itself gets a few more responses. They are not shown on the screen, but they explain its behavior.

• The {name} tool needs access level {LEVEL}, but the person chose {LEVEL}. The person changes the level in the "Global integrations" window.
• The action has started and continues in the app - it must not be treated as not done, a repeated call will do the work twice.
• Could not find out what is on the screen now: the interface thread is busy and did not answer even a short request. This usually means long work without a window - a network call or a call to an external program.

Frequently asked questions

How safe is this?

By default the assistant only reads. Nothing changes and nothing starts until you raise the access level yourself. Raise the level for the task and set it back afterwards.

Will the assistant spend my credits?

Only at the "Full, without deletion" and "Full, with deletion" levels. At these levels it is allowed to start video creation, and video creation in the cloud spends the balance. At the "Edits and previews" level only the preview starts: it does not spend the balance, but if a daily video limit applies, each preview uses one video from it.

I changed the level, but the assistant works the old way.

A new level applies to the next connection. Disconnect the assistant and connect again.

The mouse and keyboard stopped working. What happened?

The assistant opened a modal window. At that moment you are locked out, not the assistant. Ask the assistant to read this window and close it.

Can I give the VUB.mcpb file to a colleague?

No. The path to the app on your device is written inside. The connection will not work for your colleague. Let them build the file on their own device.

How many actions are available to the assistant in total?

75 in total. At the "Read only" level 34 are available, then step by step: 57, 60, 69 and 75.

Where is this setting if no project is open?

It is shared by the whole app, and it does not need a project. The "Global integrations" window opens from the menu in the header. The difference from the project window is described on the project integrations page.