Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

ParaView MCP Server

by failed33version 0.2.5i★ –iRuns on your computer
Registry nameio.github.failed33/paraview-mcp-server

Install

Overview

Description from the maker (original English)

Control ParaView through arbitrary Python code

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs on your computer
  • Transport: stdio
  • Category: Other

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on your computer with your user’s permissions (files, network, apps).
  • The registry lists no key to fill in.

You need

  • PyPIPython’s uv installed (for the uvx command)

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-server

Open in Cursor

Or copy the settings yourself

Paste 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.

Open in VS Code

Or copy the settings yourself

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.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

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

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account failed33, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Otheri

  • More stars than 0% of the other 32683 servers in this category
  • Published to the registry more recently than 76% of the other 32683 servers in this category
  • Basic checks equal to or better than 100% of the other 32683 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is ParaView MCP Server safe?

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.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

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).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.2.5) reached the registry 11 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.

What can I use instead?

In the same category: Spec Driven Development, Remote Desktop Commander, MCP Server Autocad Lisp Helper

Alternatives

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

Spec Driven Development

by formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

Runs on your computer★ 440MITUpdated 14 months ago
Install

Remote Desktop Commander

by desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

Runs in the cloud★ 211Updated 2 days ago
Install

README from the maker

Open the README

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.

ParaView MCP

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:

  • a ParaView plugin (C++/Qt) that exposes a TCP bridge inside the ParaView GUI
  • a Python MCP server that connects to the plugin and serves tools to any MCP client

Prerequisites

  • ParaView ≥ 5.13. Pre-built plugins are available for the exact versions and platforms listed below; other ParaView releases require a source build against the matching SDK.
  • uv

Quick Start

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.

Set Up the ParaView Plugin

Download a pre-built plugin binary from the latest GitHub Release. Releases provide this matrix:

PlatformArchitectureParaView versionsPackage
Linuxx86_646.2.0, 6.1.1, 6.0.1, 5.13.3.tar.gz
macOSarm64 (Apple Silicon)6.2.0, 6.1.1, 6.0.1, 5.13.3.dmg
Windowsx646.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:

  1. Open Tools > Manage Plugins in ParaView.
  2. Click Load New... and select ParaViewMCP.so (Linux/macOS) or ParaViewMCP.dll (Windows) from the plugin directory.
  3. Enable Auto Load.
  4. Open Tools > ParaView MCP.
  5. Click Start Server.

The ParaView MCP panel shows the connection status and execution history. Non-loopback binds require an auth token.

Configure Your MCP Client

Claude Code (CLI)
claude mcp add paraview -- uvx paraview-mcp-server
Claude Desktop

Add to your claude_desktop_config.json:

{

"mcpServers": { "paraview": { "command": "uvx", "args": ["paraview-mcp-server"] } } }

Other MCP Clients

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.

Configuration

The server connects to the ParaView plugin using these environment variables:

VariableDefaultRequiredDescription
PARAVIEW_HOST127.0.0.1NoHost where the ParaView plugin is listening
PARAVIEW_PORT9877NoTCP port for the plugin bridge
PARAVIEW_AUTH_TOKEN—Non-loopback onlyAuthentication token (must match the plugin setting)
PARAVIEW_CONNECT_TIMEOUT_SECONDS30NoDeadline for opening the connection and completing the hello
PARAVIEW_COMMAND_TIMEOUT_SECONDS—NoOptional 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" } } } }

Available Tools

ToolDescription
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.

Design and Differences from ParaView_MCP

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:

  1. We provide an 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.
  2. Architecturally, ParaView_MCP's own disclaimer states that it relies on synchronization between 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.

Contributing

See CONTRIBUTING.md for build instructions, development setup, and pull request guidelines.

License

MIT — see THIRD-PARTY-NOTICES.txt for dependency licenses.

Ask PopNx