Prepare the next board meeting
Ask your assistant to draft the meeting, propose the agenda, add attendees and flag calendar conflicts. The draft is created in BoardiGO for you to review — nothing goes to the board until you decide.
Your AI assistant
BoardiGO connects to AI assistants through the open MCP standard.
After a secure sign-in, your assistant can draft the next board meeting, set up a written resolution and tell you who has not signed yet — in BoardiGO, from the conversation you already work in.
We name an assistant as compatible only after verifying the connection end to end.
What you can ask for
The assistant works through the same board workflow as the app. Every draft it creates lands in BoardiGO, where you review it before anything reaches the board.
Ask your assistant to draft the meeting, propose the agenda, add attendees and flag calendar conflicts. The draft is created in BoardiGO for you to review — nothing goes to the board until you decide.
Start a circular vote from chat: the assistant prepares the resolution and its vote steps in BoardiGO, ready for you to check before it is sent to the members who need to decide.
Ask who has signed, where the minutes stand, and have reminders go to the members who still owe a signature — without opening another tab.
Turn decisions into owned tasks linked to the board workflow, and check what is still open before the next session.
The connection is tied to your BoardiGO sign-in and works on the organizations your account can access. It is a faster pair of hands — not a separate actor on your board.
How it connects
What the connection is — and how we keep the claims around it honest.
BoardiGO speaks the Model Context Protocol (MCP) — the open standard AI assistants use to reach the tools you work with. One connection, no per-vendor integration project.
The connection is authorized with a standard OAuth sign-in, WorkOS-backed — the same family as our Enterprise SSO. No API keys to copy around, and access can be revoked like any session.
Assistants that support remote MCP connections can connect. We publicly name only the assistants we have verified end to end — and the list grows as we test.
The assistant surface mirrors the board workflow — meetings, resolutions, signatures, minutes, follow-up tasks. It is a board tool, not a general data firehose.
Connect your assistant
You need an assistant that supports remote connections, a BoardiGO account, and then a sign-in. Menu names differ from one assistant to the next. We name an assistant only after we have walked these steps with it.
You connect as yourself, on the organizations your account can access. If you do not have a BoardiGO account yet, create one before you start.
Create your accountOpen your assistant's settings for connectors, integrations or MCP servers and add a remote connection with this address: https://api.boardigo.com/v1/mcp
Your assistant opens the standard BoardiGO sign-in. There is no API key to copy. Once you approve, the connection stays tied to your sign-in and can be revoked like any session.
Try "draft next month's board meeting" or "who has not signed the resolution yet?". Whatever the assistant prepares is created in BoardiGO as a draft — nothing reaches the board until you review it and send it.
Some assistants only add remote connections on certain plans or behind a developer setting. Tell us which assistant you use; we will verify it with you and add it to the list.
Tell us which assistant you useThe assistants we have verified end to end are listed here as we test them. If yours is not listed yet, tell us which one it is and we will walk the connection with you.
Get started
Create your BoardiGO account, connect the assistant your team already uses, and ask it to draft the next board meeting — or who has not signed yet. Nothing reaches the board until you review it.
Or write tointegrations@boardigo.com