MCP Server for Microsoft Paint

Created By
ghuntleya year ago
Overview

What is Paint MCP?

Paint MCP is a Rust implementation of a Model Context Protocol (MCP) server that allows programmatic interaction with Microsoft Paint on Windows systems.

How to use Paint MCP?

To use Paint MCP, clone the repository, build the project using Cargo, and start the server. You can then interact with Microsoft Paint through the provided HTTP API endpoints.

Key features of Paint MCP?

  • Connect to an existing Paint instance or launch a new one
  • Draw basic shapes (lines, rectangles, circles)
  • Select different drawing tools
  • Set colors
  • Save drawings

Use cases of Paint MCP?

  1. Automating drawing tasks in Microsoft Paint
  2. Creating custom drawing applications that leverage Paint's interface
  3. Educational purposes for understanding programmatic UI interactions

FAQ from Paint MCP?

  • Is Paint MCP compatible with all versions of Windows?

It is tested on Windows 10/11 but may not work with older versions due to UI changes.

  • Can I use Paint MCP in production?

No, it is not suitable for high-volume or production use due to its reliance on undocumented APIs and UI layouts.

  • What programming language is used for Paint MCP?

The project is implemented in Rust.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
ghuntley
Star
2
Language
Rust
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago