Local Snagit MCP Server
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Local Snagit MCP ServerRecord a demo of the signup flow in the browser"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Local Snagit MCP Server
A local MCP server that lets GitHub Copilot record demo videos with the copy of TechSmith Snagit already installed on your machine. Copilot drives the recording while it drives everything else — a terminal walkthrough, a deployment, or a Playwright session against your deployed app — and gets back an MP4.
It talks to Snagit through Snagit's own SNAGIT.VideoCapture COM automation interface, so there
are no hotkey simulations, no UI scripting, and no third-party screen recorder.
Requirements
Windows
Snagit 2023 or newer, installed and launched at least once (verified against Snagit 2025, 25.4.0.8498)
Python 3.10+
Related MCP server: snip-mcp
Setup
py -3.12 -m venv .venv
.\.venv\Scripts\python.exe -m pip install -e .
.\.venv\Scripts\python.exe -m snagit_mcp --selftest--selftest should report "ready": true. If it does not, see Troubleshooting.
The repo ships .vscode/mcp.json, so VS Code offers to start the server as soon
as you open the folder. To use it from any workspace, add the same block to your user-level
mcp.json with absolute paths instead of ${workspaceFolder}.
Recordings land in SNAGIT_MCP_OUTPUT_DIR (the workspace recordings/ folder by default, or
%USERPROFILE%\Videos\Snagit MCP when unset).
Environment variable | Default | Purpose |
|
| Where MP4s are written |
|
| Upper bound for the |
|
| How long |
Tools
Tool | What it does |
| Snagit version, COM reachability, output folder, display count |
| Monitors and their pixel bounds |
| Visible windows with handles and bounds — use it to find the browser |
| Restore and foreground a window before recording it |
| Record a display, a window, or a fixed region to MP4 |
| Whether a recording is running, and for how long |
| Skip dead air such as a deployment finishing |
| Stop, wait for encoding, return the MP4 path and duration |
| Hold a beat so the last on-screen action is readable |
| Most recent MP4s in the output folder |
There is also a record_app_demo prompt (a slash command in VS Code) that gives Copilot the full
shot-list-first procedure.
Recording a demo of a deployed app
Snagit records real pixels, so the browser has to be visible — run Playwright headed, not headless. Combined with the Playwright MCP server, a session looks like this:
Playwright MCP opens your App Service URL in a headed browser and signs in.
list_windowswithtitle_contains: "Edge"(orChrome) returns the browser window handle.start_recordingwithtarget: "window"and that handle. It returns after Snagit's countdown, so the next action is already on camera.Playwright clicks through the scenario;
waitbetween steps keeps it followable.stop_recordingreturns the MP4 path.
For a repo walkthrough that moves between VS Code, a terminal, the Azure portal, and the browser,
use target: "fullscreen" with the display_index from list_displays instead of a single window.
Ask for it in plain language, for example:
Record a demo of the deployment flow: show the prerequisites in the README, run the deploy script, then open the App Service URL and walk through creating a record. Use display 0.
How it drives Snagit
These behaviours were established by experiment and the timings in src/snagit_mcp/recorder.py depend on them:
The sequence is
Capture()to arm, a 3s settle,Start(), thenStop(). CallingStart()too soon afterCapture()produces an empty 2 KB MP4.Snagit plays a ~3.4s countdown after
Start().start_recordingabsorbs it and only returns once real recording has begun.Snagit's recording toolbar must stay visible. Setting
HideRecordingUI = Truesilently truncates recordings to a couple of seconds. The toolbar sits outside the captured region, so it does not show up in the video.Microphone and system audio are not settable over COM in this Snagit build — those setters throw, and a failed write can wedge the capture engine. Audio therefore follows whatever is configured in Snagit's own capture settings. Set it there before recording if you want narration.
RecordingDuration,FrameCountandAverageFrameRateare only meaningful afterStop(); during a recordingrecording_statusreports the server's own wall-clock instead.Output goes straight to a file. Snagit Editor does not pop up between takes.
Verifying after a Snagit upgrade
.\.venv\Scripts\python.exe tests\smoke_recording.pyRecords a real 5-second clip through the MCP tools and checks the resulting MP4's duration. If a future Snagit release changes the countdown or arming behaviour, this is what will catch it.
Troubleshooting
Symptom | Fix |
| Launch Snagit once so it registers its COM server, then retry |
Recordings are empty or a couple of seconds long | The capture engine is wedged: |
| A capture is already open in Snagit — cancel it and retry |
Region coordinates look shifted on a scaled display | The server sets per-monitor DPI awareness at startup; confirm |
A note on what ends up on camera
Screen recording captures whatever is on screen, including terminal output, tokens, portal sessions, and notifications. Close or clear anything sensitive before recording, and review the MP4 before sharing it.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
- FlicenseAqualityDmaintenanceEnables LLMs to capture screenshots and screen recordings through MCP with chunked session-based transfers for reliable image consumption. Supports multi-monitor selection, timeline capture, and compatibility with both vision and non-vision language models.111
- AlicenseNot gradedqualityDmaintenanceAn MCP server for capturing screen regions directly into Claude Code conversations via hotkeys or tool calls. It provides Windows-specific screen snipping with multi-monitor support, persistent storage, and automatic management of captured images.MIT

PixVerse MCPofficial
AlicenseNot gradedqualityFmaintenanceEnables video generation from text, images, and more through MCP-compatible apps like Claude and Cursor.52MIT- AlicenseNot gradedqualityAmaintenanceMCP server that turns any running web app into demo videos, interactive walkthroughs, and marketing captures via one command. Enables AI agents to show their work with regenerated demos on every PR.112MIT
Related MCP Connectors
MCP server for Clipkit — gives AI agents a video toolbox via the Clipkit schema.
Voice-powered bug reporting with 13 MCP tools. Record bugs by talking; let AI find and fix them.
Remote MCP for Copilot CLI switch gate MCP, structured receipts, audit logs, and reviewer-ready evid
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/paullizer/LocalSnagitMCPServer'
If you have feedback or need assistance with the MCP directory API, please join our Discord server