Mural

@Mural show me all the widgets in our Q1 Planning board so I can see what's been added this week

I retrieved 47 widgets from the Q1 Planning mural. The board contains 23 sticky notes (mostly clustered in the 'Priorities' section), 8 text boxes with headers, 6 shapes used as swimlane dividers, 5 images (product mockups), 3 connectors linking ideas, and 2 file attachments. Most recent activity shows 9 sticky notes were added in the past 7 days, primarily around the 'Marketing Launch' area. This illustrates what a typical widget inventory looks like—your actual mural may have different counts and types.

This example demonstrates the read-heavy Get Mural Widgets tool, which returns structured data about every element on a board. You'll need the exact mural ID (usually from a URL or prior lookup). The response helps you audit board state or feed content into downstream analysis, but doesn't include widget positions or detailed formatting.

@Mural create sticky notes for these three action items: 'Finalize pricing model', 'Schedule customer interviews', 'Update roadmap deck'

I created 3 sticky notes on your mural. Each note contains one of your action items as text. The notes were placed at default coordinates since no specific layout was provided—you'll likely want to drag them into the appropriate section of your board. Note IDs: sn-abc123, sn-def456, sn-ghi789. This example shows how the MCP can programmatically add content, though it doesn't auto-organize or assign owners.

This write example uses the Create Sticky Note tool to add content directly to a mural. The MCP requires a target mural ID and will place notes at default positions unless you specify coordinates. It's ideal for bulk-adding brainstorm outputs or meeting notes, but you'll still need to manually arrange and style the notes in Mural's UI afterward.

@Mural pull all file attachments from our Design Review board and summarize what assets the team has uploaded

I found 4 file widgets in the Design Review mural: 'homepage-wireframe-v3.fig' (Figma file, 2.1 MB, uploaded 3 days ago), 'user-research-findings.pdf' (PDF, 890 KB, uploaded last week), 'brand-guidelines.pdf' (PDF, 1.4 MB, uploaded 2 weeks ago), and 'prototype-demo.mp4' (video, 15 MB, uploaded yesterday). The team appears to be iterating on homepage designs while referencing research and brand standards. This illustrates typical file metadata—actual download or preview requires separate access to the linked files.

This synthesis example combines the Get Files for a Mural tool with AI reasoning to provide context about attached assets. The MCP returns file metadata (names, sizes, upload dates) but not file contents—you'd need separate integrations or manual downloads to analyze the actual documents. Useful for inventory checks or spotting missing deliverables before a review meeting.

When Mural MCP works for async brainstorm capture

A 6-person design consultancy runs client discovery workshops in Mural, then needs to pull sticky notes and file attachments into Switchy for synthesis. The MCP's create-sticky and get-widgets tools let you push AI-generated themes back onto the board or pull all notes into a Switchy thread for clustering. This works if your workshop cadence is weekly or slower—OAuth2 setup takes a few clicks per workspace, and the 5-tool scope means you're mostly moving text and files, not editing shapes or timers. If you're running daily retros or need to manipulate complex canvas objects, the MCP is too narrow. For monthly or quarterly workshops where the output is a summary doc, this MCP closes the loop between whiteboard and writeup.

Mural MCP for templated board creation at scale

A 3-person People Ops team maintains onboarding murals for each new hire cohort and wants to auto-populate sticky notes from a Switchy prompt (role-specific tasks, links, welcome messages). The create-sticky tool handles batch creation, and get-files confirms attachments landed. This scenario wins if you're spinning up 5-10 boards a month and the content is text-heavy—think checklists, not diagrams. The MCP doesn't create frames or connectors, so if your onboarding flow is a visual journey map, you'll still template that by hand. For text-based task boards where speed matters more than layout polish, the MCP cuts 20 minutes per board. Buy this if your onboarding murals are 80% sticky notes and you're tired of copy-paste.

When Mural MCP handles affinity mapping at small scale

A 4-person product team collects user interview quotes in Mural and wants AI to tag themes across 30-50 sticky notes per research sprint. The get-widgets tool pulls all notes into Switchy, where you cluster and label, then create-sticky pushes theme headers back to the board. This works if your research cadence is biweekly and your murals stay under 200 widgets—beyond that, the MCP's read-all approach gets slow and you're better off exporting CSV. The 5-tool limit also means no voting dots or timer widgets, so this is pure affinity mapping, not prioritization. If your research output is a tagged board that feeds a roadmap doc, the MCP saves 30 minutes per sprint. Skip it if you need real-time collaboration or complex board interactions.