Apps and integrations

Built-in apps give the agent capabilities you can use immediately. Connect only the services you need; the agent can then combine them with your widgets and custom tools.

Email: IMAP and SMTP

In Settings → Email, choose a provider and enter the address, servers and app password it requires. Prism tests access before saving. Gmail generally needs two-step verification followed by an app password. Outlook.com/Hotmail requires OAuth2 for mail, which the mail client does not yet support; Microsoft Calendar sign-in is separate.

Once connected, Email can read, search, reply, attach files, manage folders and move messages. AI categories are not IMAP folders. Under Inbox rules, a simple rule can move mail or mark it read based on sender, recipient or subject. Preview matches before enabling it; rules run while Prism is running, without a model call.

Proton Mail uses a local Bridge that provides its own IMAP/SMTP credentials. The Bridge must be reachable from the Prism server.

Follow the Proton Mail Bridge guide: installation, credentials and connection →

Proton Mail: install and configure Bridge

Proton Mail does not provide direct IMAP access to your mailbox. Bridge connects to Proton, decrypts messages locally and provides the IMAP and SMTP servers used by Prism. It must keep running on a machine reachable by the Prism server.

1. Install the Bridge bundled with Prism

With Prism’s standard Docker Compose setup, use the included optional service rather than installing a second application on your PC. The current Dockerfile uses an AMD64 image; this procedure does not work as-is on an ARM64 host. The container is based on a community image that packages Proton Mail Bridge.

Open a terminal in the Prism folder containing your Compose file and your .envfile. Build the service, then stop any existing instance before opening its interactive setup:

docker compose --profile protonmail build protonmail-bridge
docker compose --profile protonmail stop protonmail-bridge
docker compose --profile protonmail run --rm protonmail-bridge init

The init command prepares the container’s GPG keyring and password store, then opens the Bridge terminal. Enter the following commands one at a time, answering any prompts before continuing:

login
info
exit

With login, enter your Proton address, your Proton password and your two-factor authentication code if requested. With info, copy the username and Bridge password for the account you want to connect. Do not share this output: it contains credentials.

After leaving the Bridge terminal, start the persistent service:

docker compose --profile protonmail up -d protonmail-bridge

2. Connect Prism to this Bridge

Open Settings → Email, select ProtonMail, then fill in the fields below. The preset fills in the server settings; you can check them under Advanced — server settings.

Click Save & connect. Prism checks IMAP and SMTP access before saving the configuration. Then open Email to check incoming messages and send yourself a test message to check outgoing mail.

These hosts and ports refer to the bundled container on Prism’s Docker network. Do not substitute 127.0.0.1 : inside the Prism container, that address points to Prism itself. The supplied Compose file does not publish any Bridge ports on the host; you do not need to open ports on the internet.

3. Retrieve the password and keep the connection

To read the credentials again later, stop the service, reopen its terminal and enter info, then exit. An account already stored normally does not require another login. Then restart the service:

docker compose --profile protonmail stop protonmail-bridge
docker compose --profile protonmail run --rm protonmail-bridge init

docker compose --profile protonmail up -d protonmail-bridge

The Docker volume named protonmail in Compose keeps the account and keyring across restarts. Do not run docker compose down -v to troubleshoot: this command deletes volumes, including Prism and Bridge data. If Bridge signs you out, sign in again and recheck its credentials in Prism.

Alternative: Bridge is already installed on your PC

For a native Windows, macOS or Linux installation, download Bridge from Proton’s official website, install it and sign in to your account. On Linux, Proton also requires a secret manager such as GNOME Keyring or Pass. Select the account in Bridge, open its mailbox details or Configure email client, then copy the displayed username, password and IMAP/SMTP settings.

These credentials belong to that Bridge installation: do not mix them with those from the Docker Bridge. Copy its own ports and security mode; the internal ports 143 and 25 in the previous table do not automatically apply to the desktop application.

Check the network: a Bridge application bound to your PC’s loopback interface does not become reachable from a container simply by replacing its address with the host’s address. For the standard Compose setup, use the bundled Bridge. If Prism runs on another machine, install Bridge alongside Prism; do not publish its ports on the internet to work around this issue.

If the connection fails

• Credentials rejected: check that the account is signed in to Bridge and that you copied its generated password, rather than your Proton account password.
• Connection refused or timed out: check that the Bridge service is running and that Prism uses the correct host and ports.
• Certificate error: for the bundled Bridge, check STARTTLS and the self-signed toggle. This exception is for your local Bridge, not other mail providers.
• Keyring or vault error: run the init command before starting the service; it initializes the container’s credential store.

docker compose --profile protonmail ps protonmail-bridge
docker compose --profile protonmail logs --tail=100 protonmail-bridge

Further reading: download Bridge, install and connect an account, find mailbox details and the password, Linux prerequisites and the community Docker image used by Prism.

Calendar: local, CalDAV, Google and Microsoft

Without a connection, events and appointments live in Prism. For CalDAV, enter the URL, account and app password in Settings → Calendar , click Connect, choose the discovered calendars and save. Example URLs: iCloud https://caldav.icloud.com, Nextcloud https://YOUR-HOST/remote.php/dav, Fastmail https://caldav.fastmail.com.

Google and Microsoft require your own OAuth app: copy the redirect URI shown by Prism into that app, then authorize the account in the browser. Follow the Google steps or the Microsoft steps. OAuth consent needs the user in the browser; the agent can guide the process.

Tasks: local, CalDAV or Todoist

Tasks work immediately with Prism’s database. For CalDAV tasks, connect the account in Calendar and choose the discovered task list. For Todoist, copy your token from Todoist → Settings → Integrations → Developer, then use Settings → Calendar → Tasks via Todoist → Connect. Todoist does not return completed-task history in its active list.

In Settings → Calendar → Active sources, choose separate sources for events and tasks. Auto prefers connected sources and shows which one is currently used. The agent’s scheduled jobs appear in Tasks’ Scheduled tab, separate from personal to-dos.

Notes and Markdown vaults

Notes uses the Prism database by default. When self-hosting, mount an existing host folder with NOTES_VAULT_PATH, recreate prism-server, then choose Settings → Notes → Markdown vault with path /vault. The mount is read/write, and existing database notes are not moved automatically.

The agent can create or change a note, including one open in the editor. Add to knowledge sends a note to a document collection; embeddings must be configured first.

MCP and custom tools

An MCP server adds its tools to the agent’s catalog. In personal mode, open Settings → MCP, add its URL and select a secret if needed. Some servers require browser OAuth consent. In multi-user mode, servers belong to groups and are managed in Admin. Settings → Tools lists available tools and lets you hide those you do not want your agent to see.

You do not need an MCP server for every need: the agent can register a local Python tool, keep data in its workspace and give it an interface with a widget. Learn how tools are built.

Channels and webhooks

Settings → Channels connects a personal Telegram bot. Slack uses a deployment-wide Socket Mode app managed by an administrator; Webex is for group agents in shared mode. Settings → Webhooks creates a signed URL that starts the agent when another system sends an event. Set the instruction, target conversation and optionally {{content}} to place the payload.

A webhook normally responds immediately while the agent works in the background; enable Wait for the agent only when the sender really needs its reply. The URL token can trigger tools: protect it like a password. Use the webhook URL exactly as Prism returns it.

Let the agent guide you

Ask “Connect my CalDAV calendar,” “Create a rule for invoices,” or “Explain how to authorize Google Calendar.” It can perform permitted steps and request secrets through a secure dialog. Browser OAuth consent and administrator-only settings still require the right person.