Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Control ParaView through arbitrary Python code
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"paraview": {
"command": "uvx",
"args": [
"paraview-mcp-server"
]
}
}
}Run this in your terminal
claude mcp add paraview -- uvx paraview-mcp-serverPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"paraview": {
"command": "uvx",
"args": [
"paraview-mcp-server"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"paraview": {
"type": "stdio",
"command": "uvx",
"args": [
"paraview-mcp-server"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account failed33, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.2.5) reached the registry 11 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, MCP Server Autocad Lisp Helper
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
High-precision static analysis and debug server for AutoCAD AutoLISP (.lsp) files.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Connect ParaView to LLM assistants through the Model Context Protocol.
The Python server is built with FastMCP 3.x. Support for the 2026-07-28 MCP specification is planned once FastMCP 4 reaches a stable release.
paraview-mcp-server has two runtime parts:
First set up the ParaView plugin. Then add the Python MCP server to Claude Code in one command:
claude mcp add paraview -- uvx paraview-mcp-server
Open Tools > ParaView MCP in ParaView, start the bridge, and connect from Claude Code.
Download a pre-built plugin binary from the latest GitHub Release. Releases provide this matrix:
| Platform | Architecture | ParaView versions | Package |
|---|---|---|---|
| Linux | x86_64 | 6.2.0, 6.1.1, 6.0.1, 5.13.3 | .tar.gz |
| macOS | arm64 (Apple Silicon) | 6.2.0, 6.1.1, 6.0.1, 5.13.3 | .dmg |
| Windows | x64 | 6.2.0, 6.1.1, 6.0.1, 5.13.3 | .zip |
Choose the package that names your exact ParaView version and platform. Download its adjacent .sha256 file, verify the package, then open or extract it and follow the included INSTALL.md. Pull requests also produce corresponding platform binaries as short-lived GitHub Actions artifacts; GitHub Releases are the permanent distribution channel.
macOS release images are Developer ID-signed, notarized by Apple, and include a stapled notarization ticket. Open the .dmg, copy the contained plugin directory to a persistent location, and load ParaViewMCP.so from that copied directory. Pull-request artifacts are unsigned test builds and remain .tar.gz files.
Alternatively, build the plugin from source against a ParaView 5.13 or newer SDK. See CONTRIBUTING.md for full build instructions. Binary compatibility is release-series specific, so use a plugin built for your ParaView major.minor version.
Once installed:
ParaViewMCP.so (Linux/macOS) or ParaViewMCP.dll (Windows) from the plugin directory.The ParaView MCP panel shows the connection status and execution history. Non-loopback binds require an auth token.
claude mcp add paraview -- uvx paraview-mcp-server
Add to your claude_desktop_config.json:
{
"mcpServers": { "paraview": { "command": "uvx", "args": ["paraview-mcp-server"] } } }
Configure a local stdio MCP server with uvx as the command and paraview-mcp-server as its only argument:
{
"mcpServers": { "paraview": { "command": "uvx", "args": ["paraview-mcp-server"] } } }
Consult your client's documentation for the location and exact format of its MCP server configuration.
The server connects to the ParaView plugin using these environment variables:
| Variable | Default | Required | Description |
|---|---|---|---|
PARAVIEW_HOST | 127.0.0.1 | No | Host where the ParaView plugin is listening |
PARAVIEW_PORT | 9877 | No | TCP port for the plugin bridge |
PARAVIEW_AUTH_TOKEN | — | Non-loopback only | Authentication token (must match the plugin setting) |
PARAVIEW_CONNECT_TIMEOUT_SECONDS | 30 | No | Deadline for opening the connection and completing the hello |
PARAVIEW_COMMAND_TIMEOUT_SECONDS | — | No | Optional deadline for receiving a command result |
Defaults work for a standard local setup. Override these when connecting to ParaView on a remote machine or non-standard port:
{
"mcpServers": { "paraview": { "command": "uvx", "args": ["paraview-mcp-server"], "env": { "PARAVIEW_HOST": "192.168.1.10", "PARAVIEW_PORT": "9877", "PARAVIEW_AUTH_TOKEN": "your-token" } } } }
| Tool | Description |
|---|---|
execute_paraview_code(code) | Execute Python code inside the active ParaView session |
get_pipeline_info() | Return a JSON snapshot of the current pipeline |
get_screenshot(width, height) | Capture the active render view as a PNG image |
One command runs at a time, up to three wait in FIFO order, and further calls report busy. This prevents concurrent mutations of ParaView's shared state.
Execution results include output, diagnostics, and separate request and Python statuses. See execution and state for cancellation, timeouts, and recovery behavior.
This project follows the approach of Blender-MCP and Slicer-MCP, both of which give LLMs direct code execution inside their respective application runtimes.
The existing ParaView_MCP implementation[^1] takes a different approach, exposing a fixed set of high-level tools without access to the underlying Python runtime, which limits flexibility for custom workflows. The major differences are:
execute_paraview_code tool that runs arbitrary Python inside the ParaView session. The plugin records each execution and, when ParaView can capture a pipeline snapshot, lets the user restore the state from immediately before that execution. This makes generated scripts easier to inspect, reuse, and adapt for tasks such as batch processing.pvserver and the ParaView client. That synchronization mechanism is deprecated in recent ParaView versions and can cause incorrect application views and general stability issues. This project instead runs a plugin inside the interactive ParaView process and exposes a TCP bridge, avoiding the pvserver/client synchronization path entirely.See CONTRIBUTING.md for build instructions, development setup, and pull request guidelines.
MIT — see THIRD-PARTY-NOTICES.txt for dependency licenses.