TouchDesigner MCP

Created By
8beeeaaata year ago
MCP server for TouchDesigner
Overview

What is TouchDesigner MCP?

TouchDesigner MCP is an implementation of a Model Context Protocol (MCP) server designed for TouchDesigner, enabling AI agents to control and operate TouchDesigner projects.

How to use TouchDesigner MCP?

To use TouchDesigner MCP, install the package via npm, connect it to TouchDesigner by importing the mcp_webserver_base.tox component, and configure your AI agent to connect to the MCP server.

Key features of TouchDesigner MCP?

  • Enables AI agents to create, modify, and delete nodes in TouchDesigner.
  • Allows querying of node properties and project structure.
  • Supports programmatic control of TouchDesigner via Python scripts.

Use cases of TouchDesigner MCP?

  1. Automating the creation and management of visual nodes in TouchDesigner projects.
  2. Integrating AI-driven functionalities into interactive installations.
  3. Enhancing creative workflows by allowing AI to manipulate visual elements in real-time.

FAQ from TouchDesigner MCP?

  • What is the purpose of the MCP server?

The MCP server acts as a bridge between AI models and TouchDesigner, facilitating automated control and manipulation of projects.

  • Is there a specific environment required to run TouchDesigner MCP?

Yes, Node.js must be installed to run the MCP server.

  • Can I use any AI agent with TouchDesigner MCP?

Yes, various AI agents like Claude Desktop, Cursor, and VSCode CopilotChat can be configured to work with the MCP server.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
8beeeaaat
Star
12
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