Processing MCP Server

Created By
twelve2fivea year ago
Overview

What is Processing MCP Server?

Processing MCP Server is a tool that allows users to create visual art and games using AI through natural language commands, enabling the generation and execution of Processing sketches.

How to use Processing MCP Server?

To use the Processing MCP Server, clone the repository from GitHub, install the necessary dependencies, configure the server settings, and then interact with your AI assistant to create sketches.

Key features of Processing MCP Server?

  • Create and run Processing sketches via AI conversations.
  • Automatically saves sketches with timestamps.
  • Configurable Processing executable path and save location.
  • Simple interface for AI assistants.
  • Includes 6 ready-to-run demos for immediate use.

Use cases of Processing MCP Server?

  1. Generating simple animations like bouncing balls or spirals.
  2. Creating interactive particle effects and games.
  3. Developing generative art pieces and complex visualizations.

FAQ from Processing MCP Server?

  • Can I use Processing MCP Server for any type of visual art?

Yes! It supports a wide range of visual art and game development tasks.

  • What are the prerequisites for using this server?

You need Python 3.8+, Processing installed, and the uv package manager.

  • Is there a demo available?

Yes! You can watch a demo video showcasing its capabilities.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
twelve2five
Star
1
Language
Python
License
MIT 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