Connecting an AI tool

A moderator or admin can let an AI assistant, such as Claude, send photos and events in for review: a folder of photos from last weekend, or the events in a calendar, a newsletter or an email thread, instead of somebody uploading or typing each one.

What it can and cannot do

An assistant connected to your organization can:

It cannot see the review queue, anybody else’s photos or events, who sent them, or the screens, and it cannot approve anything. All that goes from Hypeboard to the AI company is your category names, the name of the person whose key it is, and what that assistant sent itself. Photos go from your computer straight to Hypeboard; the assistant only ever sees their file names.

Everything it sends waits for a moderator. Nothing reaches a screen until somebody approves it and chooses which screens show it, exactly like a photo or event a member sends from their phone. Assistants misread dates and pick up the wrong folder, and the queue is where you catch that.

Turning it on

  1. An admin opens Settings in the console and, under AI tools, turns on Let moderators connect AI tools. It is off until somebody does, and turning it off again stops every connected assistant at once.
  2. Open Connected agents (under Setup) and choose Connect an agent. Give it a name you will recognize later, such as “Church calendar”.
  3. Choose which AI tool you use. The dialog shows the key with the setup for that tool already filled in, ready to copy. The key is shown once; if you lose it, revoke that one and make another.

Photos and events: the connector

To send photos, the assistant needs a small program running on the computer that has them, because it reads the photos off the disk itself. Hypeboard serves that program; nothing is installed from anywhere else. It needs Node.js 20 or later on that computer.

Then ask it something like “send the photos in my Pictures folder called Picnic to Hypeboard, captioned Summer picnic”. It sends them ten at a time and tells you how far it has got. If one photo is refused it names that photo and sends the rest. A photo your organization already has is skipped, so asking again for the same folder, after adding a few more, sends only the new ones.

Every photo sent together gets the same caption. Ask for separate sends if different photos need different captions.

Copy the setup from the console rather than from this page: it names the current version of the program, and when Hypeboard is updated the assistant will say its copy is out of date. The setup is only shown with a new key, so to update, connect a new one and revoke the old.

Events only: nothing to install

If you only need events, Claude Code can connect straight to Hypeboard. Run this in a terminal, with your key in place of hba_… (or choose events only in the key dialog, which fills it in):

claude mcp add --transport http hypeboard https://hypeboard.garage.kwandrews.com/api/agent/mcp \
  --header "Authorization: Bearer hba_…"

Then ask it something like “add the events from this flyer to Hypeboard”. Other assistants that can connect to a remote MCP server take the same address, https://hypeboard.garage.kwandrews.com/api/agent/mcp, and the same Authorization header.

Once an admin has set your organization’s time zone in Settings, it uses that one. Until then it will ask which time zone your events are in, because “7pm” means a different moment in each one.

Reviewing what it sent

What an assistant sends appears in Pending photos or Pending events like anything else, under the name of the person who made the key, marked agent and followed by the key’s name — “Jane Doe · via Office Mac”. Choose Connected agent under Source to see only those. Approve it, edit it or reject it as usual; a note you type when rejecting is something the assistant can read back and tell its user.

Sending the same photo again does nothing: it is recognized and skipped, whatever its file is called. Sending the same event again updates the copy still waiting for review. Once a moderator has approved or rejected it, the assistant cannot change it; edit it in the console instead.

Stopping one

On Connected agents, revoke the key. The assistant is refused from its very next request. Blocking or locking the person who made a key, or making them a member rather than a moderator, ends their keys too, for good. What it already sent stays where it is, still labelled with the key, which now says it was revoked.