AI Assistants

You can let an AI assistant work in Chapel Screen for you. Ask it in your own words and it does the work in your account:

“Make a presentation for Sunday from these sermon notes, on our usual theme.”
“Add John 3:16–18 and Amazing Grace as quick slides to tonight's event.”
“Put the notices on the bulletin and tell the worship team in the chat.”
“Invite sam@example.com to the youth team.”

It works as you, with your permissions and no more, and only where you allow it. What it changes appears straight away for everyone who has the same thing open — just as if you had made the change yourself.

Which Assistants Work

Any AI assistant that supports MCP can be connected. MCP (the Model Context Protocol) is an open standard that lets an assistant use other services, and many assistants support it — for example Claude, ChatGPT, Cursor, Visual Studio Code with GitHub Copilot, and Gemini CLI. Chapel Screen does not favour any of them.

In your assistant's settings, look for Connectors, MCP servers, Tools or Integrations. If you can add one by its web address, it will work with Chapel Screen. Which features are available can depend on your plan with that assistant.

Connecting an Assistant

In Chapel Screen, open your profile from the user menu and choose Agents.
Under Connect an agent, click Copy to copy the address shown there.
In your assistant, add a new connector or MCP server and paste the address. Give it a name you will recognise, such as “Chapel Screen”.
The first time the assistant connects, it opens Chapel Screen in your browser. Sign in if you are asked to.
Chapel Screen shows the name the assistant gave itself and the address your answer will be sent to. Choose what it may reach (below) and click Allow.
You are sent back to your assistant, and it is ready to use. It now appears on your Agents page.

Any application can call itself anything, so check the address as well as the name. If you did not start the connection yourself, or you don't recognise the name or the address, click Deny.

Choosing What It Can Reach

Before you allow an assistant, you choose what it may see and change. There is one line for your own things, and one for each team you belong to:

Your own — the presentations and themes you own, your songs, your profile and your invitations.
Each team — what is shared with that team, its events, its bulletin and its chat.

For each line, pick one of three:

None — the assistant cannot see it at all.
Read — it can look things up and read them, but change nothing.
Change — it can also create and edit.

For example, if you only want help with the youth team's services, give the youth team Change and set everything else to None: the assistant will never see another team's presentations. If you are not sure, start with Read — you can connect it again later with more.

An assistant can never do more than you can yourself. If you are a member of a team but not one of its admins, the assistant cannot change that team's settings either.

A team the assistant creates for you, or joins when it accepts an invitation for you, is added to what it can reach. A team you join yourself later is not — connect the assistant again to give it that team.

What an Assistant Can Do

Write and edit presentations, including adding images, and set their theme and display options (text size, slides, reveal, slide content, highlight, hiding the header and footer).
Put a Bible passage or a song into a presentation, laid out as Insert Content does it, from Chapel Screen's own Bibles and song library. The passage is in the translation you name; otherwise your team's default, then yours. Only when Chapel Screen does not have a translation or song does the assistant look elsewhere, and it should tell you where the text came from.
Create themes and change their colours, fonts and images.
Plan events: add and reorder presentations, add channels, and make Bible, song and text quick slides. A team admin's assistant can also change how a channel shows a presentation — its theme, options, layout and text alignment on that screen only, such as hiding the footer on a stage screen.
Set up a team's bulletin and read or write in the team chat.
Search the song library, add songs and send them for review.
Create teams, invite people, withdraw an invitation, and accept or decline invitations sent to you.
Change your name and default Bible translation.

Some of these reach other people. Inviting someone, withdrawing an invitation or declining one sends an email, and a chat message notifies the team — just as when you do it yourself. A good assistant will check with you first.

What an Assistant Cannot Do

It cannot delete anything: no presentation, theme, event, song or team.
It cannot remove someone from a team or take back something you shared.
It cannot change your password or sign in as you.
It cannot put a presentation on air during a service — that stays with whoever is presenting.

Those things stay with you, in the app.

Disconnecting an Assistant

Every assistant you have connected is listed on your Agents page, with what it can reach and when it was last used. Click Disconnect and it stops working at once.

Changing your password also disconnects every assistant, in the same way it signs you out on your other devices. Connect them again afterwards if you still want to use them.

Assistants That Cannot Sign In, and Scripts

Most assistants open your browser to sign in, as described above. If yours cannot, or you are writing a script of your own, use a personal access token instead:

On the Agents page, under Personal access tokens, give the token a name.
Choose what it may reach, exactly as above, and how long it lasts.
Click Create token and copy the token straight away — it is shown only once.
Give it to your assistant or script as its access token (a “bearer token”). Anyone who has the token can act as you within what you allowed, so keep it as safe as a password.

Revoke a token on the same page when you no longer need it. Developers will find the full API reference linked from the Agents page.