Slack Miro integration: setup, features, plan limits and cost

“Slack Miro integration” can mean two different things. The standard Miro app for Slack creates a board from a Slack shortcut, shares board links, unfurls them, and sends Miro notifications; it does not edit board contents in Slack. A separate Miro MCP connection lets Slackbot create or update Miro content in a conversation, subject to Slackbot access and Miro’s tool-call limits. Miro also now has a beta for Mermaid diagrams that can be edited on a Miro board with code and visual changes kept in sync.

Direct answer: Use the standard Miro app to start a board, share it, and handle notifications from Slack. Connect Miro through Slackbot’s MCP app if you want to ask Slackbot to create or change a Miro board. Use Miro’s Mermaid beta when the team wants to edit a flowchart on a shared canvas. If the diagram’s discussion, edits, and change record should stay together in a Slack thread, compare that workflow with Arialine’s Slack-native diagram board.

What “Miro in Slack” includes

Route	What you do from Slack	Where the diagram is edited	Main limit to check
Miro Feed (the standard Slack app)	Create a board with a shortcut; share links; receive notifications; grant access	On the Miro board	Miro sharing permissions and the workspace’s app policy
Miro through Slackbot MCP	Ask Slackbot to read or change Miro board content	On the Miro board, through MCP actions	Slackbot message access plus Miro MCP tool-call quota
Miro Mermaid beta	Share the board in Slack, then edit the Mermaid diagram on the canvas	On the Miro board, visually or in Mermaid source	Beta availability and the diagram types supported

Only the first two rows are Slack integrations. The Mermaid beta is a feature of the Miro board, not another Slack connector. The standard app handles links, notifications and access; Slackbot MCP adds agent actions; the Mermaid beta changes how a diagram behaves inside Miro.

Set up the standard Miro app for Slack

Miro’s current instructions connect the Slack app from a user’s Miro profile: open Profile settings → Integrations → Miro Feed (Slack App) → Connect, authorize Slack, then choose which events to receive. You can also connect from Miro’s Notifications settings. A Slack workspace may require admin approval for the app or its permissions. See Miro’s Slack integration guide for the current screens and steps.

To create a board, use Slack’s Miro shortcut, search for Miro, and choose Create a board. Give it a title, select a Miro team, and add the message that will accompany the board link. The board is created in Miro and the link is posted to the selected Slack conversation.

When a Miro board link is posted, the app can show the board name, description, and thumbnail. It can also identify Slack users who do not have board access and let you invite them from the conversation. Miro notifications can include comments, mentions, invitations, and access requests, depending on each person’s notification preferences. Those are useful Slack actions, but arranging shapes and editing the board still happen on Miro’s canvas.

Use Slackbot to create or update Miro content

Miro’s MCP server is a separate route. Slack’s current MCP integration guide lists Miro as an available app and says each member connects their own account. The connection uses that user’s Miro permissions, so Slackbot can only work with boards that account can access. Miro’s MCP FAQ describes the standard connection as one team per user at a time; authorizing another team can supersede the previous connection. It also notes that Enterprise organizations can allow work across multiple teams when an admin enables MCP for the organization or selected teams. If Slackbot cannot reach a board through the active authorization, re-authenticate to the team where that board lives. Review the requested app scopes and confirm your organization’s approval policy before installation.

A basic flow is:

1. Install or update the Miro app from Slack’s Marketplace. Review its listed scopes; workspace app-approval settings may require an owner or admin to approve it. In Enterprise organizations, an org admin may need to install the app at the org level before adding it to a workspace.
2. Open Slackbot, select Apps, connect your Miro account, and authenticate to the team that contains the target board.
3. Check the access controls for your Slack plan: Enterprise Grid and Enterprise+ admins can manage MCP server and tool access; Slack says those fine-grained admin controls are unavailable on Pro, Business+, and Enterprise Select.
4. Ask Slackbot to create or update the board, including its full Miro URL so the request points to the intended board—for example, “Add a fraud-check step between checkout and payment on this Miro flowchart: paste the board URL.”
5. Open the resulting Miro board and verify the content and permissions there.

Slackbot access and Miro MCP quota are separate limits. Slack’s current Slackbot limits guide says Free and Pro users generally get a trial or preview, Business+ includes 15 messages per member per week, and Enterprise+ has no weekly or lifetime message limit. Enterprise Select and Enterprise Grid also have unlimited access when the Slack AI add-on is present. The Free and Pro preview does not reset after the included messages are used. Slack also documents Salesforce Flex Credits for extra Slackbot usage on Free, Pro, and Business+ when a Salesforce organization is connected and the required admins enable them. Slack says advanced capabilities released after June 2026, including third-party content creation and automated actions, may use limits, consumption pricing, or a hybrid model. It says it will provide 30 days’ written notice before usage-based pricing takes effect. The price example below therefore shows annual subscription list prices only; it excludes Flex Credits and any separate usage charge.

Miro counts MCP tool calls separately: its current usage table lists 100 calls a day on Free, 500 on Starter, 2,000 on Business, and 10,000 on Enterprise. Calls reset at 00:00 UTC; further calls are blocked until reset. One Slackbot request can use more than one MCP call, so a Slackbot message is not the same unit as a Miro tool call. Miro’s MCP server is available across plans, although Enterprise admins may need to enable it.

Mermaid diagrams in Miro are no longer just images

Miro’s Mermaid beta guide says Mermaid code can become a Miro diagram and that code and visual edits stay in sync. Its support matrix matters: flowcharts render as native Miro shapes and are visually editable; sequence, class, and ER diagrams also render as native shapes, but visual editing is still coming soon. Other supported Mermaid types render as non-editable SVGs, and unsupported types do not render. Miro says the beta’s supported types and capabilities are improving iteratively, so test your syntax before standardizing on it. The workflow fits a team that wants a shared canvas and code-linked diagrams, but it does not give every Mermaid type the same editing experience.

Miro’s MCP connection is a related but distinct path: a connected agent can create, read, update, and edit Mermaid diagrams on Miro boards, according to Miro’s beta guide and its MCP server FAQ. The tools and visual editor are evolving, so test the exact diagram type and edit path your team needs.

This means the old distinction “Miro is visual, Mermaid is code” is too simple. The practical choice is now about the workflow around the diagram: whether people need freeform facilitation and direct visual co-editing on a Miro board, or whether they want the Slack conversation itself to be the place where a technical diagram is requested, revised, and reviewed.

Estimate the cost using the seats you need

The vendor prices below are U.S. list prices, billed annually and shown as monthly equivalents, before tax. Miro’s current pricing page lists Starter at $8 per member per month billed annually or $10 billed monthly, and Business at $20 per member per month billed annually. Miro Free includes one workspace with three editable boards. Slack’s pricing page lists Pro at $7.25 per member per month and Business+ at $15 when billed annually; monthly rates are higher. Vendor pricing and packaging can change, so check the linked pages before buying.

For a 25-person team currently on Slack Pro that needs ongoing Slackbot access and chooses Miro Starter for all 25 members:

Cost item	Calculation	Monthly equivalent
Slack Pro → Business+	25 × ($15 − $7.25)	$193.75 additional
Miro Starter for 25 members	25 × $8	$200
Combined additional cost	Slack upgrade + Miro plan	$393.75

This scenario assumes all 25 people are Miro members and the team is upgrading from Pro. If only four people need Starter membership, the Miro portion is $32 a month; if the workspace already has Business+, do not add the Slack upgrade again. Miro Starter also offers public visitor editing, so model the people who actually need member access and check whether that sharing mode is appropriate for your board. The cost of Miro’s broader whiteboard and workshop features is part of what you are buying; this is not a like-for-like replacement price for a Slack diagram app.

Arialine serves a narrower job: creating or editing a Mermaid board from a Slack thread and retaining versions with links to the messages behind changes. It works on Slack Free, Pro, Business+, and Enterprise without requiring a Slackbot upgrade. Its current pricing page lists a Free plan with 3 boards, up to 8 versions per board, and 10 AI generations per workspace per day; Team is a flat workspace price, currently $79 monthly or $756 annually. Pasted Mermaid rendering does not consume an AI generation. This can make the price model easier to predict for a large group, but it does not provide Miro’s freeform board and facilitation features or its visual Mermaid editing workflow.

Choose by where the work continues

• Choose Miro’s standard app when the task is to create a board link, share access, or receive notifications in Slack.
• Choose Slackbot + Miro MCP when a person with access to the Miro board wants to request a change from Slack and the team has adequate Slackbot messages and Miro calls.
• Choose Miro’s Mermaid beta when reviewers want code-linked flowcharts they can edit with supported controls on a shared canvas. Miro uses automatic layout; converting to free-form allows free placement but breaks Mermaid-code sync and MCP editing. Visual editing and the code panel are available only in focus mode. Check current diagram-type support first.
• Choose a Slack-native diagram workflow when the thread is where the team asks for changes and needs the maintained diagram’s revision history to point back to those requests. See Arialine vs Miro for a fuller workflow comparison, or the Miro alternative for Slack teams for the narrower use case.