PyVista MCP Server

Created By
pyvistaa year ago
PyVista-based MCP (Model Context Protocol) server
Overview

what is PyVista MCP Server?

PyVista MCP Server is a server that integrates PyVista for 3D visualization with Model Context Protocol (MCP) tools, allowing users to create and visualize 3D models interactively.

how to use PyVista MCP Server?

To use the PyVista MCP Server, configure the server settings using the provided JSON structure and run the server. You can then use the hello_world tool to generate a 3D visualization and export it as an HTML file.

key features of PyVista MCP Server?

  • Integration of PyVista for advanced 3D visualization.
  • hello_world tool for generating a grid of 3D shapes.
  • Exporting interactive 3D visualizations as HTML files.

use cases of PyVista MCP Server?

  1. Visualizing complex 3D models for analysis.
  2. Creating interactive educational content for teaching 3D concepts.
  3. Developing applications that require real-time 3D rendering.

FAQ from PyVista MCP Server?

  • What is the Model Context Protocol (MCP)?

MCP is a protocol designed to facilitate the management and visualization of 3D models in various applications.

  • How do I configure the server?

You can configure the server using the specified JSON structure in your settings.

  • Is there a demo available?

Yes! The hello_world tool provides a simple demonstration of the server's capabilities.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
pyvista
Star
2
Language
Python
License
MIT license

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago