Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Windows screen capture MCP server with display, region, and active-window capture tools.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
CAPTURE_SCREEN_DEFAULT_DISPLAY, CAPTURE_SCREEN_OUTPUT_DIR, CAPTURE_SCREEN_HIDE_FOREGROUND_WINDOWS_TERMINALWhich app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"capture-screen": {
"command": "dnx",
"args": [
"CaptureScreenMcp",
"--yes"
],
"env": {
"CAPTURE_SCREEN_DEFAULT_DISPLAY": "your-value",
"CAPTURE_SCREEN_OUTPUT_DIR": "your-value",
"CAPTURE_SCREEN_HIDE_FOREGROUND_WINDOWS_TERMINAL": "your-value"
}
}
}
}Run this in your terminal
claude mcp add capture-screen --env CAPTURE_SCREEN_DEFAULT_DISPLAY=your-value --env CAPTURE_SCREEN_OUTPUT_DIR=your-value --env CAPTURE_SCREEN_HIDE_FOREGROUND_WINDOWS_TERMINAL=your-value -- dnx CaptureScreenMcp --yesFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"capture-screen": {
"command": "dnx",
"args": [
"CaptureScreenMcp",
"--yes"
],
"env": {
"CAPTURE_SCREEN_DEFAULT_DISPLAY": "your-value",
"CAPTURE_SCREEN_OUTPUT_DIR": "your-value",
"CAPTURE_SCREEN_HIDE_FOREGROUND_WINDOWS_TERMINAL": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"capture-screen": {
"type": "stdio",
"command": "dnx",
"args": [
"CaptureScreenMcp",
"--yes"
],
"env": {
"CAPTURE_SCREEN_DEFAULT_DISPLAY": "your-value",
"CAPTURE_SCREEN_OUTPUT_DIR": "your-value",
"CAPTURE_SCREEN_HIDE_FOREGROUND_WINDOWS_TERMINAL": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
CAPTURE_SCREEN_DEFAULT_DISPLAY envCAPTURE_SCREEN_OUTPUT_DIR envCAPTURE_SCREEN_HIDE_FOREGROUND_WINDOWS_TERMINAL envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account ochtum, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (1.0.5) reached the registry 7 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need .NET on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, sync. labs
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Lipsync videos, dub them into other languages, make talking videos and open sync. Studio.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Windows 向けのローカル実行型 MCP サーバーです(stdio transport)。 C# / .NET 10 の .NET tool として NuGet.org に公開しており、画面キャプチャとキャプチャ画像削除ツールを提供します。
io.github.ochtum/capture-screenCaptureScreenMcpcapture-screen-mcpcapture_screen / capture_display / capture_region 実行時に、撮影領域に重なった Windows Terminal を一時的に非表示化(既定で有効)list_displays()capture_screen(outputPath?: string)capture_display(display?: int | string, outputPath?: string)capture_region(x: int, y: int, width: int, height: int, outputPath?: string)capture_active_window(outputPath?: string)delete_all_capture_images()delete_capture_images_by_datetime(targetDate?: string, startDatetime?: string, endDatetime?: string)dnx を使用します。dotnet run を使用します。CAPTURE_SCREEN_DEFAULT_DISPLAYcapture_display で display 省略時の既定値primary, left, right, プライマリ, 左, 右, 2CAPTURE_SCREEN_OUTPUT_DIRC:\capture_screen)CAPTURE_SCREEN_HIDE_FOREGROUND_WINDOWS_TERMINAL1/true/on で有効、0/false/off で無効NuGet.org の公開済みパッケージを MCP クライアントから起動する場合は、dnx で CaptureScreenMcp を実行します。
{
"servers": { "capture-screen": { "type": "stdio", "command": "dnx", "args": ["CaptureScreenMcp@1.0.5", "--yes"], "env": { "CAPTURE_SCREEN_OUTPUT_DIR": "C:\\capture_screen", "CAPTURE_SCREEN_DEFAULT_DISPLAY": "primary", "CAPTURE_SCREEN_HIDE_FOREGROUND_WINDOWS_TERMINAL": "1" } } } }
通常の .NET tool としてインストールして起動することもできます。
dotnet tool install --global CaptureScreenMcp --version 1.0.5
capture-screen-mcp
dotnet restore
dotnet build
dotnet run --project src
開発中にソースツリーを直接参照する場合の接続設定例です。
{
"servers": { "capture-screen": { "type": "stdio", "command": "dotnet", "args": ["run", "--project", "src"], "env": { "CAPTURE_SCREEN_OUTPUT_DIR": "C:\\capture_screen", "CAPTURE_SCREEN_DEFAULT_DISPLAY": "primary", "CAPTURE_SCREEN_HIDE_FOREGROUND_WINDOWS_TERMINAL": "1" } } } }
src/CaptureScreenMcp.csproj の を更新します。.mcp/server.json のトップレベル version と packages[0].version を同じバージョンに更新します。dotnet pack src/CaptureScreenMcp.csproj -c Releasedotnet nuget push src/bin/Release/*.nupkg --api-key --source https://api.nuget.org/v3/index.jsonこのパッケージは NuGet MCP サーバーとして認識されるため、以下を含めています。
.mcp/server.jsonREADME.md の コメントPackageIcon に指定した icon.pngMcpServer package typePackAsTool / ToolCommandName)NuGet.org への公開だけでは、registry.modelcontextprotocol.io には自動掲載されません。 NuGet.org のパッケージ検証が完了してから、MCP Publisher で .mcp/server.json を公開します。
mcp-publisher login github
mcp-publisher publish .mcp/server.json
server.json の name と、NuGet パッケージに含まれる README.md の mcp-name は一致している必要があります。 また、packages[0].version は mcp-name が一致する NuGet パッケージのバージョンを指している必要があります。
CAPTURE_SCREEN_OUTPUT_DIR 直下の画像ファイルを削除します。server.json.mcp/server.json