Stormboard
An online sticky note whiteboard making meetings, brainstorms, and creative projects more productive and effective.
Verdict
Common use cases
- Capture brainstorm ideas during video calls
- Organize sprint retrospective feedback visually
- Link related concepts across planning sessions
- Tag and categorize feature requests in real time
- Archive completed project boards as read-only
Integration
- Vendor
- Stormboard
- Category
- productivity
- Auth
- API_KEY
- Tools
- 41
- Composio slug
stormboard
Tools
- Accept a Storm Invite
Tool to accept a Storm invitation and join the Storm. Use when a user wants to accept an invitation to join a Storm.
- Add a Favorite Star
Tool to add a favorite star to a Storm on the Dashboard. Use when you need to mark a Storm as a favorite.
- Check Authentication
Tool to verify API key authentication validity. Use when you need to test if the API credentials are valid and properly configured.
- Close a Storm
Tool to close an open Storm, making it read-only. Use when you need to prevent further changes to a Storm. Only the Storm creator or a Storm administrator can close a storm.
- Create a Line Connector
Tool to create a line connector between two ideas. Use when you need to establish a connection between a pair of ideas on the Storm board.
- Create a new chat message
Tool to create a new chat message in a Stormboard storm. Use when you need to post a message to a specific storm's chat.
- Create a New Storm
Tool to create a new Storm in Stormboard for interactive planning and collaboration. Use when you need to create a digital workspace for brainstorming, planning, or team collaboration.
- Create a New Tag
Tool to create a new tag in a Storm without any data related to Ideas. Use when you need to add a new tag to a Storm's tag collection.
- Create a New User
Tool to create a new user account in Stormboard. An email will be sent to the newly created user asking them to verify their account. Use when you need to add a new user to the system.
- Create an idea in Stormboard
Tool to create a new idea in an existing Stormboard storm. Use when you need to add ideas, notes, or items to a storm with specific content and details.
- Create Tag Data for an Idea
Tool to update tag data for an idea. Any tag not in the change list remains unchanged. Tags not found in the Storm are created automatically with the provided tag data applied.
- Decline a Storm Invite
Tool to decline a Storm invitation and remove it from your list. Use when a user wants to reject an invitation to join a Storm.
- Delete a Connector Between Ideasdestructive
Tool to delete a line connector between two ideas. Use when you need to remove a connection between a pair of ideas on the Storm board.
- Delete a Specific Connectordestructive
Tool to delete a line connector using the connector ID. Use when you need to remove a specific connector from the Storm board.
- Duplicate a Storm
Tool to duplicate an existing Storm. Use when you need to create a copy of a Storm with all its content.
- Get a list of connectors in a Storm
Tool to retrieve a list of connectors within a specific Storm. Use when you need to access relationship data between ideas or elements in a Storm.
- Get a List of Ideas
Tool to retrieve all ideas from a Storm. Returns a list of ideas, but Files, Images, and Whiteboards do not contain their corresponding data at this time. Use when you need to get an overview of all ideas in a Storm.
- Get A List Of Participants
Tool to retrieve a list of all participants in a Storm. Use when you need to see who has access to a specific Storm and their roles.
- Get A List Of Storms Invites
Tool to retrieve a list of storms that you have been invited to. Use when you need to see pending storm invitations for the authenticated user.
- Get A List Of Your Storms
Tool to retrieve a list of storms from Stormboard. Use when you need to browse or access available storms in the user's account.
- Get Authentication Info
Tool to retrieve authentication information and API token for the authenticated user. Use when you need to get authentication details or verify API access credentials.
- Get Chat Messages
Tool to retrieve a list of chat messages from a Stormboard storm. Use when you need to view the chat history for a specific storm.
- Get Idea Data
Tool to retrieve detailed data and metadata for a specific idea. Use when you need to fetch information about an idea including its content, position, creator, votes, comments, and associated task details.
- Get Info About Your User
Tool to retrieve authenticated user profile information. Use when you need to get the current user's details like name, email, or account metadata.
- Get List of Tags in Storm
Tool to retrieve the list of tags that have been created in a Storm. Use when you need to view all tags available in a specific Storm. Note that tag data for individual ideas is not available through this endpoint.
- Get My Storm Access
Tool to check if the authenticated user has access to a Storm and retrieve their permission level. Use when verifying user permissions for a specific Storm. Returns 401 error if user lacks access.
- Get Storm Details
Tool to retrieve detailed information about a specific Storm. Use when you need to get complete Storm details including metadata, settings, and configuration.
- Get Storm Template
Tool to retrieve template data for a Storm including all sections and subsections. Use when you need to get the organizational structure and template configuration of a Storm.
- Get Tag Data For An Idea
Tool to retrieve tag data for a specific idea in Stormboard. Use when you need to view all tags associated with a particular idea.
- Get Unread Chat Messages
Tool to retrieve unread chat messages from a specific Storm. Use when you need to check for new messages in a Storm's chat.
- Invite Participants to Storm
Tool to invite people to join a Storm by email. Use when you need to add new participants to a Storm.
- Join a Storm
Tool to join a Storm using its ID and access key. Use when a user wants to add themselves to a Storm's participant list.
- Mark Chat Messages as Read
Tool to mark all chat messages as read in a Storm. Use when you need to mark all unread chat messages in a specific Storm as read.
- Remove a Favorite Stardestructive
Tool to remove a favorite star from a Storm on the Dashboard. Use when you need to unmark a Storm as a favorite.
- Reopen a Storm
Tool to reopen a closed Storm. Use when you need to reopen a previously closed Storm. Note: You must be a Storm administrator or the team owner to perform this action.
- Update a Line Connector
Tool to update a specific line connector between two ideas. Use when you need to modify the label or style properties of an existing connector.
- Update Notifications
Tool to update user notification preferences. Use when you need to enable or disable email notifications for the authenticated user.
- Update Section in Storm
Tool to update a section's title, description, and/or character in a Storm. Use when you need to modify section properties. Note: You must be a Storm administrator to perform this action.
- Update Storm Legend
Tool to update the color labels of the legend for a storm. Use when you need to customize the legend labels for storm items. You must be the storm creator or a storm administrator to perform this action.
- Update Your Profile
Tool to update your user profile information. Use when you need to modify the authenticated user's first name or last name.
- Verify Your Account
Tool to verify a Stormboard account using a verification code. Use when you need to confirm account ownership or complete the account verification process.
Setup
Setup guide
- 11. Open your Switchy workspace and navigate to Settings > Integrations > Add Integration. 2. Search for Stormboard and click Connect. 3. Log into your Stormboard account at stormboard.com, go to Account Settings > API Access, and generate a new API key. 4. Copy the key and paste it into the Switchy prompt when asked. 5. Click Authorize to complete the connection. 6. Test it by opening any Space and typing '@Stormboard check authentication' — you should see a confirmation that the key is valid. 7. To use a tool, @mention Stormboard in a message and describe what you want (e.g. '@Stormboard create a new Storm called Q2 Roadmap Planning'). 8. The MCP will execute the action and return a summary or ID you can reference in follow-up prompts.
What teammates see: by default, memories from Stormboard are scoped to the Space (PROJECT visibility) - you can mark any memory PRIVATE or share it ORG-wide.
Works well with
Top models
Compatibility data appears once enough Spaces have used this MCP together with a given model.
How Switchy teams use it
Starter prompts
Launch Planning Storm
@Stormboard create a new Storm called 'Q3 Product Roadmap Workshop'. Set it up so the team can start adding ideas right away.Open in a Space →
Connect Related Ideas
@Stormboard create a line connector between idea #12345 and idea #12348. These two features should ship together.Open in a Space →
Tag Feedback by Theme
@Stormboard create a new tag called 'High Priority' in Storm #67890. We'll use it to mark the most urgent items.Open in a Space →
Post Chat Update
@Stormboard post a chat message in Storm #67890 saying 'All ideas from today's session are now tagged. Review by EOD Thursday.'Open in a Space →
Close Completed Storm
@Stormboard close Storm #67890. The roadmap is finalized and we don't want any more edits.Open in a Space →
Example outputs
Illustrative - representative of the model's voice and quality, not literal recordings.
@stormboard list all my active Storms and show which ones have unread chat messages or recent activity in the last 48 hours
Based on your Stormboard account, here are your active Storms: **Q1 Product Roadmap** (12 ideas, 3 unread messages) - Last activity 6 hours ago by Sarah Chen **Customer Feedback Sprint** (8 ideas, 0 unread) - Last activity 18 hours ago by you **Marketing Campaign Ideas** (15 ideas, 7 unread messages) - Last activity 2 hours ago by Mike Torres This is an illustrative example showing how the MCP would surface Storm metadata including message counts and recent contributors.
This example demonstrates read-only data retrieval across multiple Storms. Requires API key with read access to your Storms. The MCP can fetch Storm lists and metadata, but the exact fields returned depend on your account's Storm configuration and permissions.
@stormboard create a new Storm called 'Website Redesign Kickoff' and add three starter ideas: 'Mobile-first approach', 'Accessibility audit', and 'Performance benchmarks'
I've created the Storm 'Website Redesign Kickoff' in your Stormboard workspace. Three initial ideas have been added: 1. 'Mobile-first approach' (Idea ID: 4521) 2. 'Accessibility audit' (Idea ID: 4522) 3. 'Performance benchmarks' (Idea ID: 4523) The Storm is now open and ready for team collaboration. You can invite teammates or continue adding ideas. This example shows the typical response structure after Storm and idea creation.
This showcases the MCP's write capabilities for creating Storms and populating them with ideas. Be aware this creates real artifacts in your Stormboard account—you'll need to manually delete test Storms if experimenting. API key must have Storm creation permissions.
@stormboard review all ideas in the 'Q1 Product Roadmap' Storm and group them by theme, then create tags for each theme and apply them to the relevant ideas
I've analyzed the 12 ideas in your 'Q1 Product Roadmap' Storm and identified three themes: **Performance** (4 ideas): Database optimization, Caching layer, API response times, Load testing **User Experience** (5 ideas): Onboarding flow, Dashboard redesign, Mobile app, Dark mode, Search improvements **Infrastructure** (3 ideas): CI/CD pipeline, Monitoring setup, Backup strategy I've created three tags ('Performance', 'User Experience', 'Infrastructure') and applied them to the corresponding ideas. This illustrative example shows how AI reasoning can organize Storm content and use the MCP to apply structural changes.
This example pairs AI analysis with multiple MCP tool calls (reading ideas, creating tags, applying tags). Demonstrates the MCP's strength in batch operations. Note that tag creation and application are separate API calls, so this workflow may hit rate limits on large Storms with 50+ ideas.
Use-case deep-dives
When Stormboard beats a Zoom call for distributed retros
A 6-person engineering team across three time zones runs their sprint retro in Stormboard instead of forcing everyone into a 90-minute call. The PM creates a new Storm with sections for 'what worked', 'what didn't', and 'action items'. Engineers drop ideas throughout the day, vote with favorite stars, and use line connectors to link related problems. The chat tool lets people clarify without scheduling another meeting. This works when your team already writes things down and trusts async collaboration. If your culture defaults to talking everything out live, the board sits empty and you're back to Zoom. The 41 tools give you enough structure to run a real process without learning a new platform every quarter.
Why agencies use this MCP for billable workshop deliverables
A 3-person consulting shop runs a strategy workshop with a client's 8-person leadership team. They create a Storm during the session, capture ideas in real time, tag themes as they emerge, and close the Storm at the end to lock the artifact. The client gets a read-only link as the official workshop output, and the agency uses chat messages to add follow-up notes without reopening the board. This beats Google Docs because the spatial layout shows how ideas connect, and it beats Miro because Stormboard's API key auth lets the MCP automate setup and teardown without manual clicks. The threshold: if your workshops are under 20 participants and you bill for deliverables, this MCP turns facilitation into a repeatable service offering.
When to skip this MCP for roadmap planning
A product manager at a 40-person startup wants to collect roadmap input from sales, support, and engineering. Stormboard's invite and tagging tools could work, but the 41-tool surface area is overkill when you just need a voting board. If your roadmap process is 'drop ideas, vote, rank', a lighter tool like a Notion database or Linear project does the job with half the onboarding friction. Stormboard wins when you need the full spatial canvas—line connectors between features and customer pain points, sections for different quarters, chat threads on specific ideas. If your stakeholders won't engage with a visual board or you're just collecting a ranked list, the MCP adds complexity you don't need. Save it for when the relationships between ideas matter as much as the ideas themselves.
Frequently asked
What does the Stormboard MCP do in Switchy?
It lets AI agents create and manage Stormboard collaborative workspaces directly from chat. Agents can spin up new Storms, post ideas, connect concepts with line connectors, tag content, send chat messages, and close boards when planning wraps. You skip the Stormboard UI entirely — the AI handles board creation, invites, and content organization based on your conversation.
Do I need admin access to connect Stormboard MCP?
You need a Stormboard API key, which any account holder can generate from their settings. You don't need workspace admin rights to connect the MCP, but certain tools — like closing a Storm or managing invites — only work if your Stormboard account has creator or admin permissions on the specific board you're targeting.
Can the MCP edit existing ideas on a Stormboard?
The current tool set focuses on creating new content — new Storms, ideas, tags, chat messages, and line connectors. It can close boards and accept invites, but editing or deleting existing ideas isn't exposed. If you need to revise content, you'll still open Stormboard directly or use their web API outside this MCP.
Why use this instead of just opening Stormboard?
Speed and context. If you're already planning in Switchy chat, the AI can scaffold a Storm, populate it with tagged ideas, and invite teammates without you switching tabs. It's faster for routine board setup. For complex visual layouts or whiteboard-style collaboration, Stormboard's native canvas still wins — this MCP handles the structured data layer.
Who on the team should connect the Stormboard integration?
Whoever owns your team's Stormboard workspace and generates API keys. That person's Stormboard permissions determine what the AI can do — if they can't close Storms or manage invites in Stormboard, the MCP can't either. One connection per workspace is typical; multiple connections only make sense if you're juggling separate Stormboard accounts.