What you can do with the Walnut MCP

Once you connect Walnut to Claude, ChatGPT, or Codex, you can ask about your Walnut account and make changes in plain language. This article lists what the Walnut MCP can do and who can use each capability.

Who can do what

What you can do depends on two things:

• Your Walnut role. Anyone in your account can build and publish Demos, translate Templates, search and organize the library, check and change the settings of their Demos, Playlists, and Deal rooms, and analyze how they perform. Demo analytics, users and seats, member management, and ownership transfers are limited to Account owners and Company admins.
• The access level you approved. When you connect, you choose between Full access (read and make changes) and Read-only (read without changing anything). With Read-only access, your assistant can answer questions but can't change anything in Walnut.

The Walnut MCP works with the same permissions you have in Walnut. Your assistant only sees, and only changes, the Templates, Demos, Playlists, and Deal rooms that you can access yourself.

Capability	Anyone	Account owners & Company admins	Needs Full access
Build a Demo	✅	✅	✅
Publish, personalize, and republish Demos	✅	✅	✅
Translate Templates	✅	✅	✅ (to start a translation)
Search your library	✅	✅
Demo performance analysis	✅	✅
Playlist and Deal room analysis	✅	✅
Audit and change Demo settings	✅	✅	✅ (to make changes)
Playlist and Deal room settings	✅	✅	✅ (to make changes)
Organize your library	✅	✅	✅
Share items	✅	✅	✅
Duplicate items	✅	✅	✅
Demo analytics		✅
Users, seats, and activity		✅
Transfer ownership		✅	✅
Manage members and invitations		✅	✅ (to make changes)

Available to everyone

Build a Demo

Needs Full access.

Ask your assistant for a Demo, and it builds one with you in the chat, from your Screens Library.

1. Two quick questions. Your assistant asks how the Demo will be used (pre/post-call or leave-behind, live call demo, new feature announcement, or website embed) and who it's for. If you've also connected a CRM, a call recorder, or a calendar (for example Salesforce, HubSpot, Gong, or Google Calendar) and you name a prospect, your assistant looks them up there and suggests answers, such as "Live call demo, because you meet them on Thursday."
2. Reuse first. If an existing Demo or Template already fits, your assistant offers it. You can share an existing Demo link as it is, or publish a new link from its Template.
3. Approve the outline. To build something new, your assistant writes a short outline, one step per feature, from the screens in your Screens Library. Approve it or ask for changes. A step your library has no screen for is left out, and your assistant tells you.
4. Review the plan. Walnut prepares a plan you can open as a page: the screens in order, their sections, the guide steps, and the links between screens. The walkthrough always opens with a welcome step on the first screen — naming the prospect's company when the brief gave one — and ends with a closing step that recaps what the viewer should walk away believing, together with a short label for the Demo's final call-to-action button. Ask for changes, such as rewording a guide step, changing where a link goes, swapping the CTA label, or adding, removing, or swapping a screen. A plan stays open for 24 hours.
5. Build it. Once you approve the plan, Walnut builds the Template and publishes a shareable Demo from it, with the welcome step, every guide step, and the closing step rolled into one on-screen walkthrough and the screens linked for click-through. You get both links, plus anything worth checking, such as links that AI picked or a screen with no way forward.

For example:

• "Build a Demo for Acme's VP of Sales to watch after our call."
• "I need a website embed Demo that shows our reporting features to marketing leaders."

New Demos are built only from screens in your Screens Library. The Templates and Demos you already have are offered for reuse, but never copied into a new build.

Publish, personalize, and republish Demos

Needs Full access.

• Publish a new Demo link from any Template you can present, whether you just built it or it's one of your team's existing Templates. Your assistant shows you a preview before it publishes.
• Personalize it. If the Template has text variables, such as the customer's company name, your assistant asks for a value for each one, or lets you keep the default. If the Template has no variable where you need one, name the text to replace (for example, "Demo Inc") and your assistant turns it into a variable, after showing you every place it was found.
• Republish a Demo to put the Template's latest changes and languages on a Demo that's already published, just like clicking Update in Walnut. You need edit access to the Demo.

A new Demo opens for anyone with the link and never expires, unless you ask otherwise. It asks for an email first only when it's a website embed. You can change any of this afterwards with the Demo settings.

For example:

• "Publish a Demo from the Platform Tour Template for Globex, with their company name in it."
• "Republish the Acme Demo so it picks up the German translation."

Translate Templates

Needs Full access to start a translation.

Translate a Template into another language without leaving the chat. Before anything starts, your assistant shows you what will be translated, how many screens and guides the Template has, that the translation uses AI credits, and how many languages the Template already has against your limit.

• Choose what to translate: the guides (with their annotations and voice-over), the text on the screens, or both.
• Keep terms as they are. Give a list of brand or product names to leave untranslated, or the exact translation to use for a term.
• Set a tone, such as "formal" or "friendly and direct".
• Shared Templates. If other published Demos come from the same Template, your assistant asks whether to add the language to the shared Template or translate a copy instead.

The translation runs in the background, and your assistant follows its progress for you. When it's done, viewers see the new language only after the Demo is republished, so your assistant offers to republish it. You can also ask whether a Demo already has a language, and get its share link for that language.

For example:

• "Translate the Enterprise Overview Template into German. Keep 'Walnut' and 'Buyer Xpert' in English."
• "How is the French translation of the Onboarding Template going?"

Search your library

Find Templates, Demos, Playlists, Deal rooms, and Deal room templates by name, folder, tag, owner, or when they were last played or updated. Each result shows its owner and folder.

Account owners and Company admins search the whole company's library. Everyone else searches the items they can access. An admin can ask for only their own items instead.

• "Find all Demos with 'onboarding' in the name."
• "What's in the Q3 Campaigns folder?"

Demo performance analysis

Rank your Demos against each other, or take a close look at one Demo, and compare the results with a company-wide benchmark.

• Compare Demos on completion, unique visitors, average view duration, or bounce rate.
• Analyze one Demo: sessions, unique visitors, view duration, completion, bounce rate, lead form conversion, and email gate collection rate, each shown next to the company benchmark. You can also break the results down by device, country, embedded vs. direct link, or viewer type.

For example:

• "Which of my Demos has the best completion rate?"
• "How is the Product Overview Demo performing compared to our other Demos?"

Demos with very few sessions are listed separately so they don't skew the ranking. The benchmark is left out when your company doesn't have enough comparable Demos yet.

Playlist and Deal room analysis

Take a close look at one Playlist or Deal room, or rank several against each other, over the last 30 days or a window of up to 90 days.

• Analyze a Playlist: sessions, unique visitors, average and median time spent, coverage (how many of the Playlist's items viewers opened), and bounce rate. You also get a per-item breakdown ranked by opens, and the items nobody opened.
• Analyze a Deal room: sessions, identified stakeholders (people who gave their email) and anonymous sessions, new vs. returning stakeholders, time spent, last activity, coverage, and the most-viewed items. It also reports:
  • Mutual Action Plan progress: completed tasks per stage, and any overdue tasks.
  • CRM deal status: the linked Salesforce or HubSpot deal's stage, amount, close date, and owner. If the room isn't linked to a deal, the rest of the analysis still works.
• Compare Playlists or Deal rooms on coverage, visitors (identified stakeholders, for Deal rooms), time spent, or bounce rate. You can narrow the comparison by tag, folder, or owner.

Results are shown next to a company-wide benchmark when your company has at least five comparable Playlists or Deal rooms. Items with fewer than 10 sessions are listed separately in a comparison.

For example:

• "Which items in the Q4 Onboarding Playlist does nobody open?"
• "How is the Acme deal room doing? Are any action plan tasks overdue?"
• "Rank our Deal rooms by stakeholder count for the last 60 days."

Audit and change Demo settings

Full access needed to make changes. Read-only access can still audit.

Ask about how your Demos are set up for the people they're sent to, and change those settings across one Demo or many at once. Selections can be made by a specific list of Demos, by name, by owner, by folder (directly or including every subfolder), or by tag.

For each Demo, your assistant can report:

• When it expires, or that it never does
• Whether an access code is required (the code itself is never shared)
• Who can open it — anyone with the link, anyone with an email, anyone with a work email, only certain people or domains, everyone except certain people or domains, or no one — and the people and domains that list refers to
• Whether non-work emails (like gmail.com) are allowed through the email gate
• Email verification state (on, off, or locked on)
• Who's emailed when the Demo is viewed — specific Walnut members, the CRM deal owner, the CRM account owner
• The link options: highlight clickable elements, show guides, guides toolbar, show the share button to viewers, show the pre-flight presenter config screen, and whether the Demo is readable by LLMs
• Whether Buyer Xpert is on
• The share link a buyer opens

For example:

• "Which of my Demos never expire?"
• "List every Demo anyone with the link can open, grouped by folder."
• "Which Demos in the APAC folder still let @competitor.com in?"
• "Which of my Demos have Buyer Xpert off?"

With Full access, your assistant can also change those same settings — expiry, access code, who can open the Demo, the email gate, non-work emails, the allowed and blocked people-and-domain lists (add, remove, or replace the whole list), who's emailed on view, each link option, whether LLMs can read the Demo, and Buyer Xpert on or off. Access codes are something you choose — your assistant will ask you for one rather than make one up, and never repeats it back. Only Account owners and Company admins can turn Buyer Xpert on or off, and only in workspaces that have it. Being readable by LLMs only takes effect while anyone can open the Demo with no email gate or access code.

Changes always run preview-then-confirm. The preview shows, per Demo, each setting's from → to, plus any Demo that can't be changed and the reason (for example, you can't edit it, or its owner has locked it) — along with any settings you asked for that this tool doesn't support yet (like welcome messages, language picker, email verification, branding, lead forms, or playback), reported back rather than silently dropped. Nothing is written until you confirm the preview.

A single change can affect up to 100 Demos. For anything bigger, narrow the selection — for example by folder, owner, or tag — and run it in batches.

:::info Changing a link option creates a new share link Turning a link option on or off creates a new share link for each affected Demo. Links already sent out keep their old options. The confirm reply gives you the current share link for each changed Demo — the same one the Share button in Walnut produces — so send that one going forward. :::

Playlist and Deal room settings

Needs Full access to make changes.

Review and change the sharing settings of Playlists, Deal rooms, and Deal room templates, one at a time or in bulk.

Review settings. For each item, see who can open it, its expiration date, whether it needs an access code (the code itself is never shown), its allowed and blocked people and domains, whether non-work emails are allowed, whether Email Verification is on, and who gets view notifications. You can filter, for example, to items that never expire, are open to anyone, or allow a specific domain.

Change settings. Update expiration dates, access codes, who can open the item, the email gate, non-work emails, allowed and blocked people and domains, and view notifications, for up to 100 items at a time. As with Demos, your assistant asks you for an access code rather than making one up.

Deal room templates are included only when you ask for them. Their settings are what each new Deal room made from them starts with.

As with other bulk changes, your assistant first shows a preview of every change and anything it will skip, and asks you to confirm.

For example:

• "Which of my Deal rooms are open to anyone with the link?"
• "Set all Playlists in the Events folder to expire on December 31."
• "Block @competitor.com from every Deal room I own."

Page-level gates inside a Deal room aren't included. Manage those in the Deal room editor.

Organize your library

Needs Full access.

Tidy up your library in bulk:

• Rename items, one by one or with find and replace
• Move items into a folder, or move a whole folder
• Create folders
• Tag and untag items (tags are only removed from items, never deleted)
• Archive items, and restore archived ones

For example:

• "Archive every Demo in the Old Campaigns folder."
• "Tag all Playlists owned by Dana with 'EMEA'."
• "Replace '2025' with '2026' in the names of my Templates."

When you ask for broad changes, your assistant shows you a preview of exactly which items will be affected and asks you to confirm. When you name the exact items, the change happens right away. If you're about to archive a Demo that's still used in a published Playlist or Deal room, your assistant always warns you first. A single change can affect up to 500 items. For anything bigger, narrow it down, for example by folder or owner.

Share items

Needs Full access.

• Make items public or private. Share Templates, Demos, Playlists, or Deal rooms with your whole company, or make them private again. Making a folder public also makes the Templates and Demos directly inside it public, and your assistant shows you that before it confirms.
• Add collaborators. Give specific members or groups view or edit access to items or to a folder. Members whose role can't edit get view access instead, and your assistant tells you.

For example:

• "Share all Templates in the Onboarding folder with the whole company."
• "Give the Sales Engineering group edit access to the Q4 Demos."

Duplicate items

Needs Full access.

Make a copy of a Template, Playlist, Deal room, or Deal room template, optionally with a new name and in a different folder. By default, the copy is named "Copy of" followed by the original name.

• The copy belongs to you, without the original's collaborators.
• A copied Playlist or Deal room is an unpublished draft with its own new link. A copied Deal room has no invitees and isn't linked to a deal.
• A copied Deal room template stays a template.
• Published Demos can't be duplicated. Duplicate their Template instead.

To duplicate a Playlist, Deal room, or Deal room template, you need access to it and the Editor, Company admin, or Account owner role. To duplicate a Template, you need permission to copy it.

For example:

• "Duplicate the Acme deal room as 'Globex deal room' in my Q4 folder."

The copy is made as soon as you ask, without a preview.

Account owners and Company admins only

Demo analytics

Ask about how prospects engage with your Demos over a date range: session counts, completions, bounces, average duration, interactions, and screen views. You can also break results down by viewer type, embedded vs. direct link, country, or top Demos.

• "How many Demo sessions did we have last week?"
• "What were our top 10 Demos this month?"
• "Compare embedded vs. direct-link sessions for the last 90 days."

Users, seats, and activity

• Users and activity: everyone in your Walnut account, with their role, last login, and how many Demos, Templates, and Playlists they created over a date range.
• Seats and licenses: total, used, and remaining seats, broken down by Editor, Presenter, and Viewer where your plan tracks seats per role. Pending invitations are counted separately.

For example:

• "How many users do we have in our Walnut account?"
• "How many Editor seats do we have left?"
• "Who created the most Demos last quarter?"

Last login is the last time someone signed in to Walnut in a browser. Activity through the API or the Walnut MCP doesn't count.

Transfer ownership

Needs Full access.

Reassign library items to another person, either a selection of items or everything one person owns.

• "Transfer all of Alex's Demos to Jordan."
• "Move ownership of everything Sam owns to Priya."

When you transfer everything someone owns, your assistant always shows you a count of each item type first and asks you to confirm.

Manage members and invitations

With Read-only access you can look up members, list pending invitations, and preview what someone owns before offboarding them. You need Full access to invite people, change roles, cancel invitations, or offboard someone.

• Find members by name or email.
• Invite people, up to 100 at once, each with their own role. Walnut checks that you have enough seats first, and invites nobody if you'd run short.
• See pending invitations, including when each one expires.
• Cancel an invitation to free up its seat right away.
• Change someone's role. Your assistant tells you if the new role has no seats left.
• Offboard someone. Your assistant first shows everything they own, then transfers all of it to the person you choose and removes their access.

For example:

• "Invite maya@example.com and li@example.com as Viewers."
• "Which invitations are still pending?"
• "Make Jordan a Company admin."
• "Offboard Alex and give their work to Jordan."

:::warning Offboarding can't be undone Offboarding someone removes their access to Walnut, signs them out, and revokes their API key. You can't undo it. To bring them back, invite them again as a new member. Their previous work stays with the person it was transferred to. :::

Some changes are always refused. For example, you can't change the Account owner's role, make someone the Account owner, demote yourself, or offboard yourself.

Share your feedback

We're adding new capabilities to the Walnut MCP all the time. Tell your Walnut account team what you'd like it to do next.