Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Cinema-quality science visualization for AI agents — headless VTK via MCP.
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.
VIZNOIR_RENDER_BACKEND, VIZNOIR_OUTPUT_DIRYou 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": {
"viznoir": {
"command": "uvx",
"args": [
"viznoir"
],
"env": {
"VIZNOIR_RENDER_BACKEND": "your-value",
"VIZNOIR_OUTPUT_DIR": "your-value"
}
}
}
}Run this in your terminal
claude mcp add viznoir --env VIZNOIR_RENDER_BACKEND=your-value --env VIZNOIR_OUTPUT_DIR=your-value -- uvx viznoirFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"viznoir": {
"command": "uvx",
"args": [
"viznoir"
],
"env": {
"VIZNOIR_RENDER_BACKEND": "your-value",
"VIZNOIR_OUTPUT_DIR": "your-value"
}
}
}
}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": {
"viznoir": {
"type": "stdio",
"command": "uvx",
"args": [
"viznoir"
],
"env": {
"VIZNOIR_RENDER_BACKEND": "your-value",
"VIZNOIR_OUTPUT_DIR": "your-value"
}
}
}
}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.
VIZNOIR_RENDER_BACKEND envVIZNOIR_OUTPUT_DIR envThese 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 8, 2026
The registry name was verified with the GitHub account kimimgo, 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.10.1) reached the registry 5 months 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, Thalovant MCP
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ 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.
Connect MCP clients to Thalovant control-plane and hub runtime APIs over stdio or Streamable HTTP.
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.
VTK is all you need. Cinema-quality science visualization for AI agents.
*One prompt → physics analysis → cinematic renders → LaTeX equations → publication-ready story.*
An MCP server that gives AI agents full access to VTK's rendering pipeline — no ParaView GUI, no Jupyter notebooks, no display server. Your agent reads simulation data, applies filters, renders cinema-quality images, and exports animations, all headless.
Works with: Claude Code · Cursor · Windsurf · Gemini CLI · any MCP client
pip install viznoir
pip install "viznoir[mesh]" # meshio + trimesh (50+ formats) pip install "viznoir[composite]" # Pillow + matplotlib (split_animate) pip install "viznoir[all]" # everything
Requires Python ≥3.10. VTK wheel auto-installed (EGL headless rendering supported).
mcp-server-viznoir --help # server entry point
python -c "import viznoir; print(viznoir.version)"
Add to your MCP client config (claude_desktop_config.json, ~/.cursor/mcp.json, etc.):
{
"mcpServers": { "viznoir": { "command": "mcp-server-viznoir", "env": { "VIZNOIR_DATA_DIR": "/path/to/your/simulation/data", "VIZNOIR_OUTPUT_DIR": "/path/to/output" } } } }
Then ask your AI agent:
*"Open cavity.foam, render the pressure field with cinematic lighting, then create a physics decomposition story."*
All tool implementations are importable as async functions. You provide a VTKRunner and await the result:
import asyncio
from viznoir.core.runner import VTKRunner from viznoir.tools.inspect import inspect_data_impl from viznoir.tools.render import render_impl
async def main(): runner = VTKRunner()
meta = await inspect_data_impl(file_path="cavity.foam", runner=runner) print(meta["fields"], meta["timesteps"])
result = await render_impl( file_path="cavity.foam", field_name="p", runner=runner, colormap="Cool to Warm", camera="isometric", width=1920, height=1080, output_filename="pressure.png", ) print(result.file_path)
asyncio.run(main())
See docs for the full tool reference.
| Category | Tools |
|---|---|
| Rendering | render · cinematic_render · batch_render · volume_render |
| Filters | slice · contour · clip · streamlines · pv_isosurface |
| Analysis | inspect_data · inspect_physics · extract_stats · analyze_data |
| Probing | plot_over_line · integrate_surface · probe_timeseries |
| Animation | animate · split_animate |
| Comparison | compare · compose_assets |
| Export | preview_3d · execute_pipeline |
22 tools · 12 resources · 4 prompts · 50+ file formats (OpenFOAM, VTK, CGNS, Exodus, STL, glTF, …)
Every frame below is a single MCP tool call. No GUI, no post-processing, no ParaView. Annotations are rendered inside the 3D scene via VTK-native text actors and leader lines — no Photoshop, no matplotlib overlay.
| | | | | | |:-:|:-:|:-:|:-:|:-:| | | | | | | | Medical CT skull volume | CFD Combustion streamlines | Thermal Heatsink gradient | Geoscience Seismic wavefield | Automotive DrivAerML · 8.8M cells | | | | | | | | Molecular H₂O electron density | Vascular Cerebral aneurysm MRA | Planetary Bennu · 196K triangles | Structural Cantilever FEA stress | Volume Thermal threshold |
Seven presets convert raw simulation data into publication-ready motion — each binds a rendering primitive to a physical phenomenon.
| Preset | Physics | Rendering |
|---|---|---|
streamline_growth | Lagrangian advection | Particle path-line extension over time |
clip_sweep | Pressure gradient cross-section | Moving clip plane |
layer_reveal | CT density classification | Progressive isosurface stacking |
iso_sweep | Orbital topology | Isovalue sweep with camera orbit |
warp_oscillation | Structural mode shape | Warp-by-vector harmonic displacement |
light_orbit | Oblique illumination | Rotating key light for material reveal |
threshold_reveal | Feature hierarchy | Threshold peeling from outside → in |
compose_assets)*Inspect → render → annotate → compose → narrate. One prompt produces a 4-panel physics decomposition with LaTeX-rendered governing equations.*
Layouts: story (vertical narrative) · grid (N×M comparison) · slides (16:9 keynote) · video (MP4 with transitions)
Full interactive gallery: https://kimimgo.github.io/viznoir/#showcase
prompt "Render pressure from cavity.foam"
│ MCP Server 22 tools · 12 resources · 4 prompts │ VTK Engine readers → filters → renderer → camera │ EGL/OSMesa headless · cinematic lighting Physics Layer topology analysis · context parsing │ vortex detection · stagnation points Animation 7 physics presets · easing · timeline │ transitions · compositor · video export Output PNG · WebP · MP4 · GLTF · LaTeX
| 22 MCP tools | 24 VTK filters |
| 10 domains | 19 native file formats |
| 6/6 VTK data types | 50+ formats via meshio |
Homepage: kimimgo.github.io/viznoir
Developer docs: kimimgo.github.io/viznoir/docs — full tool reference, domain gallery, architecture guide
MIT