Creates Storms, adds ideas and the connectors between them, posts and reads Storm chat, and invites participants by email.
41actions available
Every action runs live through MCP. Nothing to build, nothing to maintain.
Ayro posts a message to a Stormboard storm conversation. Team members collaborate and stay informed in real time.
Ayro retrieves chat messages from a Stormboard storm. Participants review discussion history and decisions.
Ayro sends invitations to add people to a brainstorming storm. Team leaders quickly assemble the right group for planning.
Each card is one request a support team gets, and the Stormboard actions Ayro runs to close it.
Ayro creates the Storm, adds each point as its own idea, and draws the line connectors that show which ideas depend on which, so a discussion arrives structured rather than as a wall of notes.
Ayro reads the ideas on a Storm, the chat messages nobody has opened yet, and the Storm metadata around them, so someone joining late gets the state of the board instead of scrollback.
Ayro creates the tags a Storm needs, applies them to individual ideas while leaving tags outside the change list untouched, and renames a section so the structure matches how the team is using it.
Ayro invites people to a Storm by email, lists who already has access and in what role, and checks the permission level of the connected account before it attempts to change anything.
How it works
Connect once, then just ask. There is no workflow builder to learn and nothing to maintain — Ayro reads the Stormboard actions it has and picks the ones a request needs.
Authorize the Stormboard account your team already uses — one consent screen, no API keys, no mapping tables. Ayro can only do what you granted that account, and you can disconnect it at any time.
Describe the job the way you would hand it to a teammate. Ayro maps it to the Stormboard actions that close it and chains as many as the request needs.
The agent runs the actions inside the conversation the customer is already in, so nobody copies data between tabs and your team can take over at any point.
Get started freeStormboard · Ayro
What can you do in Stormboard without me setting anything up?
These, right away:
Great, let's start with the first one.
FAQ
Setup, permissions, and the limits of what Ayro can do inside Stormboard.
Closing a Storm makes it read-only, but only the Storm creator can run Close a Storm, and Reopen a Storm requires a Storm administrator or the creator. Whether Ayro can do either therefore depends on the role of the account behind the connection, not on the toolkit.
All 41 actions your agent can call on Stormboard, straight from the live MCP connection.
Accept a Storm invitation and join the Storm.
Add a favorite star to a Storm on the Dashboard.
Verify API key authentication validity.
Close an open Storm, making it read-only.
Create a line connector between two ideas.
Create a new chat message in a Stormboard storm.
Create a new Storm in Stormboard for interactive planning and collaboration.
Create a new tag in a Storm without any data related to Ideas.
Create a new user account in Stormboard.
Create a new idea in an existing Stormboard storm.
Update tag data for an idea.
Decline a Storm invitation and remove it from your list.
Delete a line connector between two ideas.
Delete a line connector using the connector ID.
Retrieve detailed information about a specific Storm.
Duplicate an existing Storm.
Retrieve a list of connectors within a specific Storm.
Retrieve all ideas from a Storm.
Retrieve a list of all participants in a Storm.
Retrieve a list of storms that you have been invited to.
Retrieve the list of tags that have been created in a Storm.
Retrieve a list of storms from Stormboard.
Retrieve authentication information and API token for the authenticated user.
Retrieve a list of chat messages from a Stormboard storm.
Retrieve detailed data and metadata for a specific idea.
Retrieve authenticated user profile information.
Check if the authenticated user has access to a Storm and retrieve their permission level.
Retrieve template data for a Storm including all sections and subsections.
Retrieve tag data for a specific idea in Stormboard.
Retrieve unread chat messages from a specific Storm.
Same connection, same setup. Pick the next one your team already uses.
Pulls current Basecamp project status into the conversation and triggers updates on request.
Reads timesheets and timecards for any period, opens projects and tasks and starts timers on them, and moves timesheets through approval.
Searches the backlog with JQL, files properly typed issues with attachments, transitions and assigns them, and moves work into the live sprint.
Files tasks with priority, due date, and assignee, answers what is on someone's plate, reworks the plan when priorities move, and leaves context behind.
Raises corrective actions with an owner and a due date, reports where open issues stand, and looks up assets by their code straight from the conversation.
Filters live task lists, captures and closes tasks in one line, reorganises sections and ordering, and manages project collaborators.

Authorize the account and your agent has all 41 actions from the first conversation.
