MCP server for controlling ParaView via AI assistants
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"paraview-mcp-python","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# ParaView MCP Server Control ParaView with AI assistants through the Model Context Protocol (MCP). `paraview-mcp-python` provides an MCP server and a ParaView-side bridge. MCP clients such as Codex CLI and Claude Desktop can use it to inspect a ParaView session, open datasets, apply filters, color data, run ParaView Python, and export screenshots. The MCP server command is: ```bash paraview-mcp-server ``` <img width="1280" height="720" alt="ParaView MCP Server demonstration" src="https://github.com/user-attachments/assets/6e21f408-72b6-4523-a527-55b283b9e274" /> ## Architecture The GUI workflow has four components: | Component | Runs in | Purpose | |---|---|---| | MCP client | Codex CLI, Claude Desktop, or another MCP host | Starts the MCP server and calls its tools. | | MCP server | Standard Python environment | Communicates over MCP stdio and forwards calls to ParaView over TCP. | | ParaView bridge | `pvpython` process | Receives JSON commands over TCP and executes `paraview.simple` operations. | | ParaView runtime | `pvserver` and a ParaView GUI client | Owns the shared session used by the GUI and bridge. | ParaView Python plugins and VTK timer callbacks are pipeline-extension mechanisms, not a general-purpose remote-control interface for a live GUI process. This project therefore uses ParaView's client/server model. `paraview-mcp-launch` starts a local `pvserver`, connects the ParaView GUI as the first client, and then connects a `pvpython` bridge to the same session. ```text ┌──────────────────────────────┐ stdio ┌────────────────────────┐ │ MCP Client │ ◄──────────────► │ MCP Server │ │ Codex / Claude / other host │ │ paraview-mcp-server │ └──────────────────────────────┘ └──────────┬─────────────┘ │ JSON/TCP │ 127.0.0.1:9876 …
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.