3D Slicer▌
by zhaoyouj
3D Slicer bridges medical professionals with advanced image analysis and Python tools; a unique alternative to Prusa Sli
Bridges medical professionals with 3D Slicer's medical imaging platform, enabling MRML node listing and direct Python code execution for advanced image analysis and visualization tasks.
Both formats append explainx.ai attribution and the canonical URL for this MCP server listing.
best for
- / Medical researchers analyzing imaging data
- / Healthcare professionals automating Slicer workflows
- / Developers building medical imaging applications
- / AI-assisted medical image analysis
capabilities
- / List and filter MRML nodes in 3D Slicer
- / Execute Python code directly in Slicer environment
- / Capture screenshots of slice views and 3D renderings
- / Control medical image processing workflows remotely
- / Manipulate 3D medical imaging scenes
what it does
Connects AI assistants to 3D Slicer for medical image analysis, enabling remote control and visualization of medical imaging workflows through natural language commands.
about
3D Slicer is a community-built MCP server published by zhaoyouj that provides AI assistants with tools and capabilities via the Model Context Protocol. 3D Slicer bridges medical professionals with advanced image analysis and Python tools; a unique alternative to Prusa Sli It is categorized under developer tools. This server exposes 3 tools that AI clients can invoke during conversations and coding sessions.
how to install
You can install 3D Slicer in your AI client of choice. Use the install panel on this page to get one-click setup for Cursor, Claude Desktop, VS Code, and other MCP-compatible clients. This server runs locally on your machine via the stdio transport.
license
MIT
3D Slicer is released under the MIT license. This is a permissive open-source license, meaning you can freely use, modify, and distribute the software.
readme
# MCP-Slicer - 3D Slicer Model Context Protocol Integration
[English](README.md) | [简体中文](README_zh.md)
[](https://www.python.org/)
[](https://opensource.org/licenses/MIT)
[](https://pypi.org/project/mcp-slicer/)

MCP-Slicer connects 3D Slicer with model clients like Claude Desktop or Cline through the Model Context Protocol (MCP), enabling direct interaction and control of 3D Slicer. This integration allows for medical image processing, scene creation, and manipulation using natural language.
## Features
1. **list_nodes**: List and filter Slicer MRML nodes and view their properties
2. **execute_python_code**: Execute Python code in the Slicer environment
3. **capture_screenshot**: Capture real-time screenshots of Slicer views
- Full application window (including module panels)
- Individual slice views (Red/Yellow/Green)
- 3D rendering view
- Enables complete REACT loop with visual feedback
## Installation
### Prerequisites
- 3D Slicer 5.8 or newer
- Python 3.13 or newer
- uv package manager
**If you're on Mac, please install uv as**
```bash
brew install uv
```
**On Windows**
```bash
powershell -c "irm https://astral.sh/uv/install.ps1 | iex"
```
and then
```bash
set Path=C:\Users
ntra\.local\bin;%Path%
```
Otherwise installation instructions are on their website: [Install uv](https://docs.astral.sh/uv/getting-started/installation/)
**⚠️ Please install UV first**
### Claude for Desktop Integration
Go to Claude > Settings > Developer > Edit Config > claude_desktop_config.json to include the following:
```json
{
"mcpServers": {
"slicer": {
"command": "uvx",
"args": ["mcp-slicer"]
}
}
}
```
### Cline Intergration
```json
{
"mcpServers": {
"slicer": {
"command": "uvx",
"args": ["mcp-slicer"]
}
}
}
```
## Usage
### Check Claude Settings
Make sure you see the corresponding slicer tools added to the Claude Desktop App
### Open Slicer Web Server
1. Open the Slicer Web Server module,
2. ensure the required interfaces are checked,
3. then start the server
## Examples
### - list_nodes
> What Markups nodes are in the Slicer scene now, list their names, what is their length if it is a line, and what is its angle if it is an angle
### - execute python code
> Draw a translucent green cube of 8 cm in the Slicer scene, mark its vertices, and then draw a red sphere inscribed in it.
### - capture_screenshot
> Capture the current state of Slicer to provide visual feedback to AI
**Usage examples:**
- `capture_screenshot()` - Capture full application window
- `capture_screenshot(view_type="slice", view_name="red")` - Capture Red slice view
- `capture_screenshot(view_type="3d", camera_axis="A")` - Capture 3D view from anterior
This enables a complete REACT loop where AI can:
1. **Reason** about what to do
2. **Act** using `execute_python_code`
3. **Observe** the result using `capture_screenshot`
## Technical Details
Utilizes existing Slicer Web Server interfaces. For technical details, please see [Slicer web server user guide](https://slicer.readthedocs.io/en/latest/user_guide/modules/webserver.html)
## Limitations & Security Considerations
- The `execute_python_code` tool allows running arbitrary Python code in 3D Slicer, which is powerful but potentially dangerous.
**⚠️ Not recommended for production use.**
- Complex operations may need to be broken down into smaller steps.
## Contributing
Contributions are welcome! Feel free to submit Pull Requests.
## Disclaimer
This is a third-party integration project, not developed by the 3D Slicer team.FAQ
- What is the 3D Slicer MCP server?
- 3D Slicer is a Model Context Protocol (MCP) server profile on explainx.ai. MCP lets AI hosts (e.g. Claude Desktop, Cursor) call tools and resources through a standard interface; this page summarizes categories, install hints, and community ratings.
- How do MCP servers relate to agent skills?
- Skills are reusable instruction packages (often SKILL.md); MCP servers expose live capabilities. Teams frequently combine both—skills for workflows, MCP for APIs and data. See explainx.ai/skills and explainx.ai/mcp-servers for parallel directories.
- How are reviews shown for 3D Slicer?
- This profile displays 52 aggregated ratings (sample rows for discoverability plus signed-in user reviews). Average score is about 4.5 out of 5—verify behavior in your own environment before production use.
Use Cases▌
Extended AI Capabilities
Add new capabilities to Claude beyond text generation
Example
Access external data sources, execute code, interact with tools and services
Transform Claude from chatbot to action-taking agent
Context Enhancement
Provide Claude with access to relevant context and data
Example
Load project documentation, access knowledge bases, query databases
Get more accurate, context-aware responses
Workflow Automation
Automate multi-step workflows combining AI and external tools
Example
Research → Summarize → Create document → Send notification
Complete complex tasks end-to-end without manual steps
Implementation Guide▌
Prerequisites
- ›Claude Desktop 0.7.0+ or Cursor IDE with MCP support
- ›Basic understanding of MCP architecture and capabilities
- ›Access credentials for integrated services (if required)
- ›Willingness to experiment and iterate on configuration
Time Estimate
15-60 minutes depending on server complexity
Installation Steps
- 1.Install MCP server: npm install -g [package-name] or via GitHub
- 2.Add server configuration to ~/.claude/mcp.json
- 3.Provide required credentials and configuration
- 4.Restart Claude Desktop to load new server
- 5.Test basic functionality with simple prompts
- 6.Explore capabilities and experiment with use cases
- 7.Document successful patterns for reuse
Troubleshooting
- ⚠MCP server not loading: Check config syntax, verify installation
- ⚠Connection errors: Check network, firewall, credentials
- ⚠Feature not working: Read server docs, check required parameters
- ⚠Performance issues: Monitor resource usage, check for network latency
- ⚠Conflicts with other servers: Check port assignments, namespace collisions
Best Practices▌
✓ Do
- +Read server documentation thoroughly before setup
- +Start with simple use cases to validate functionality
- +Test in non-production environment first
- +Monitor resource usage and performance
- +Keep servers updated for bug fixes and new features
- +Document configuration for team members
- +Use environment variables for sensitive configuration
✗ Don't
- −Don't grant overly permissive access to MCP servers
- −Don't skip reading security considerations in docs
- −Don't expose sensitive data without proper controls
- −Don't run untrusted MCP servers without code review
- −Don't ignore error messages—investigate root cause
💡 Pro Tips
- ★Combine multiple MCP servers for powerful workflows
- ★Create custom MCP servers for your specific needs
- ★Share successful configurations with team
- ★Use MCP inspector for debugging
- ★Join MCP community for tips and troubleshooting
Technical Details▌
Architecture
Model Context Protocol standardizes how AI hosts (Claude, Cursor) communicate with external tools and data sources through server implementations.
Protocols
- Model Context Protocol (MCP)
- JSON-RPC 2.0
- stdio or HTTP transport
Compatibility
- Claude Desktop
- Cursor IDE
- Custom MCP clients
When to Use This▌
✓ Use When
Use when you need Claude to access external data, execute actions, or integrate with tools. Best for extending AI capabilities beyond conversation.
✗ Avoid When
Avoid when native integrations exist (use official APIs directly), for real-time critical systems, or when security/compliance requires zero external dependencies.
Integration▌
- →Tool composition: Chain multiple MCP tools in workflows
- →Context augmentation: Provide AI with relevant external data
- →Action delegation: Let AI execute tasks on external systems
- →Bidirectional sync: Keep AI context and external systems in sync
Discussion
Product Hunt–style comments (not star reviews)- No comments yet — start the thread.
List & Promote Your MCP Server
Share your MCP server with the developer community
Ratings
4.5★★★★★52 reviews- ★★★★★Isabella Johnson· Dec 28, 2024
According to our notes, 3D Slicer benefits from clear Model Context Protocol framing — fewer ambiguous “AI plugin” claims.
- ★★★★★Shikha Mishra· Dec 16, 2024
Strong directory entry: 3D Slicer surfaces stars and publisher context so we could sanity-check maintenance before adopting.
- ★★★★★Naina Huang· Dec 16, 2024
Useful MCP listing: 3D Slicer is the kind of server we cite when onboarding engineers to host + tool permissions.
- ★★★★★Henry Patel· Dec 12, 2024
I recommend 3D Slicer for teams standardizing on MCP; the explainx.ai page compares cleanly with sibling servers.
- ★★★★★Ira Jain· Dec 12, 2024
We evaluated 3D Slicer against two servers with overlapping tools; this profile had the clearer scope statement.
- ★★★★★Isabella Garcia· Nov 19, 2024
3D Slicer is among the better-indexed MCP projects we tried; the explainx.ai summary tracks the official description.
- ★★★★★Mia Srinivasan· Nov 11, 2024
Strong directory entry: 3D Slicer surfaces stars and publisher context so we could sanity-check maintenance before adopting.
- ★★★★★Henry Malhotra· Nov 7, 2024
3D Slicer is a well-scoped MCP server in the explainx.ai directory — install snippets and categories matched our Claude Code setup.
- ★★★★★Mia Agarwal· Nov 3, 2024
3D Slicer has been reliable for tool-calling workflows; the MCP profile page is a good permalink for internal docs.
- ★★★★★Henry Sethi· Oct 26, 2024
We wired 3D Slicer into a staging workspace; the listing’s GitHub and npm pointers saved time versus hunting across READMEs.
showing 1-10 of 52