# Create a product walkthrough from Cursor Source: https://www.ngram.com/docs/cursor-product-walkthrough Published: 2026-11-03T00:00:00Z Updated: 2026-11-03T00:00:00Z Turn an approved change summary into a video brief in Cursor. Learn what to include, when to add real footage and how to review the result before sharing. Developer Use an approved release summary and footage to brief a walkthrough from Cursor. [Open ngram](https://www.ngram.com/app) [All docs](https://www.ngram.com/docs) ## Read before this Read these direct prerequisites in order. Each guide lists any earlier context it assumes. 1. [1 MCP server Connect an eligible MCP client to ngram tools.](https://www.ngram.com/docs/mcp) ## When to use this guide Use this if you ship software from Cursor and need a customer-facing walkthrough of a release. Suppose a change adds a role picker to team invitations. The pull request explains the implementation, but a new admin needs to see which role to choose and what a pending invite looks like. Have the approved change summary and current screenshots or footage ready. ## Step 1. Connect Cursor to ngram Get the cursor-plugin folder from the [official plugin repository](https://github.com/ngramdata/ngram-plugins/tree/main/cursor-plugin?utm_source=www.ngram.com) . Copy its contents, including the hidden .cursor-plugin directory, into ~/.cursor/plugins/local/ngram, then reload the Cursor window. In Customize → Plugins, open ngram and authenticate its MCP server. If local plugins are restricted, ask your admin to enable them. The [MCP guide](https://www.ngram.com/docs/mcp) explains what the connected account can do. The [Cursor integration page](https://www.ngram.com/integrations/cursor) also shows a release brief and a concept lesson. Cursor documents where to inspect connected MCP tools when the plugin loads but a tool is missing. [Cursor’s MCP documentation](https://cursor.com/docs/mcp?utm_source=ngram.com) . ## Step 2. Prepare the evidence for the invitation flow Consider a release that lets an account admin pick a role before sending a teammate invitation. The code may mention a permissions enum and an invitation record. A new admin cares about a different sequence: find Invite, enter the address, choose the role, send, and recognize Pending. Confirm the labels and order against the released screen. If your source only establishes the new permissions behavior, keep the script at that level until you have the screen capture. Prepare three small inputs for Cursor: the approved release sentence, the viewer’s starting state and the evidence of success. For this example the starting state is an account admin with an unused invitation. The evidence is a pending invitation with the role the admin chose. A private ticket full of unrelated implementation details makes a poorer brief than those three inputs. Write the invitation sequence into the brief before asking Cursor to create anything. You can settle the settings and price in Cursor. Its MCP creation job then runs through production without pausing for you to approve a storyboard or sign in to a website. ## Step 3. Write a brief for the admin sending the invite Try this brief: “Make a short walkthrough for a new account admin. Show the invitation sequence: open Invite, pick the member role, then send. End with how to tell the invitation is pending. Preview the settings and cost before creating.” Use the actual field labels from the release. Omit email addresses, private ticket links and unrelated implementation details. Decide where the footage will come from before you start the job. If you already have an approved recording of the role picker, supply it with the brief. If you need ngram to visit the app, start a video in ngram Studio and give it the product link. [Browser Handoff](https://www.ngram.com/docs/browser-handoff) happens there: you sign in on the site and choose Done so ngram can continue. Cursor cannot hand over the browser. ## Step 4. Review the quote and start the job Ask Cursor to prepare the video settings and quote the cost. Once you confirm, it starts the job and returns a project link. Use the same job to check progress and retrieve the finished video. For changes to the result, open the project in ngram. Keep the job ID or Studio project link returned for that request. If the wait times out, ask for the status of that same job before submitting the brief again. ## Step 5. Check the walkthrough using a sample invitation Open the result as if you were the new admin. Can you distinguish a member from an administrator? Does the final scene show how to recognize a pending invitation? Use [video editing](https://www.ngram.com/features/video-editing) for a scene correction. If a teammate only needs to copy a command or find a setting, send the written instruction instead. When the result opens, try this test: mute it and point to the exact control an account admin would use to invite another person. If that control belongs only to admins, the title and opening must say so. Next, listen without looking. Can you tell when to choose the role relative to pressing Send? Correct the scene that introduces the wrong order. For a tutorial that must match the released product, supply the approved recording of the picker and the resulting pending row. A conceptual animation can explain why roles matter. It cannot establish the spelling or location of a button in your customer's workspace. ## Step 6. Correct the scene and save the brief for the next release If the finished cut spends too long introducing the product, open the project in ngram. Ask for one specific change: “Start at the role picker, use the supplied footage and end on the pending invitation.” The moment a reviewer needs an exact label unavailable in the source, stop revising the prompt and obtain the released screen. Another fluent description cannot establish what customers actually see. Keep a small note near the release PR with five fields: viewer, starting state, one change, source screen and visible finish condition. For the invitation example, the finish condition includes both role and Pending. For a reporting release, it might be a CSV containing the expected rows after a filter. The form stays the same; the evidence changes with the task. ## References and next steps - [ngram for Cursor](https://www.ngram.com/integrations/cursor) — check the plugin setup and supported video workflow. - [Connect ngram over MCP](https://www.ngram.com/docs/mcp) — troubleshoot the connection to your external AI client. - [Browser Handoff](https://www.ngram.com/docs/browser-handoff) — collect product footage when a website asks you to sign in. ## Continue in ngram Open the workspace and put this guide into practice with your own project. [Open ngram](https://www.ngram.com/app)