Interactive Drawing MCP

Created By
AaronGoldsmitha year ago
MCP Server for collaborative drawing with Large Language Models
Overview

What is Interactive Drawing MCP?

Interactive Drawing MCP is a collaborative drawing server that utilizes the Model Context Protocol (MCP) to provide an interactive drawing interface using Tkinter.

How to use Interactive Drawing MCP?

To use the Interactive Drawing MCP, clone the repository, install the package, and run the server to open the drawing window. You can also use it with the Goose CLI for enhanced functionality.

Key features of Interactive Drawing MCP?

  • Drawing Grid Interface: A 16x16 grid where each cell can be toggled between filled and empty states.
  • Server Capabilities: Start drawing sessions, toggle cell colors, and retrieve grid states.
  • Persistence: Saves grid state to a JSON file for consistency across sessions.
  • Real-Time UI Update: Automatically updates the UI based on changes to the grid state.

Use cases of Interactive Drawing MCP?

  1. Collaborative drawing sessions among multiple users.
  2. Educational tools for teaching grid-based drawing concepts.
  3. Prototyping interactive applications that require real-time visual feedback.

FAQ from Interactive Drawing MCP?

  • Can I use Interactive Drawing MCP for solo projects?

Yes! It can be used for both collaborative and individual drawing projects.

  • Is there a way to reset the drawing grid?

Yes! There is a clear grid button that resets all cells to their initial state.

  • How does the real-time UI update work?

A background thread monitors the grid state file and updates the UI whenever changes are detected.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
AaronGoldsmith
Star
0
Language
Python
License
-

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
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