Blender 3D Network Visualization
Create stunning 3D network topology visualizations in Blender from CDP/LLDP neighbor data. Network engineers can request topology drawings via natural language, and NetClaw translates neighbor discovery data into 3D rendering commands.
When to Use
- Visualizing network topology in 3D for presentations
- Creating topology diagrams from CDP/LLDP neighbor data
- Exporting network diagrams as PNG images
- Customizing device colors and adding labels
- Demonstrating network architecture to stakeholders
MCP Server
- Server:
blender-mcp (community MCP via uvx)
- Command:
uvx blender-mcp (stdio transport)
- Host: Windows running Blender with BlenderMCP addon (port 9876)
- Requirements: Blender 3.0+, BlenderMCP addon installed and connected
Available Tools
| Tool |
Parameters |
What It Does |
get_scene_info |
None |
Returns current Blender scene objects |
create_object |
type, name, location, scale |
Creates primitives (cube, sphere, cylinder) |
modify_object |
name, position?, rotation?, scale? |
Transform position/rotation/scale |
set_material |
object_name, color, metallic?, roughness? |
Apply colors and materials |
execute_blender_code |
code |
Run arbitrary Python in Blender |
Workflow Examples
Draw Network Topology
# Draw topology from CDP/LLDP data
"Draw the network topology in Blender using CDP data"
# Visualize neighbors for a specific device
"Visualize the CDP neighbors for core-rtr-01 in 3D"
# Create diagram from LLDP data
"Create a 3D network diagram from the LLDP data"
# Quick topology request
"Show me the network topology in Blender"
Export Visualization
# Export as PNG
"Export the Blender scene as topology.png"
# Save the diagram
"Save the network diagram as a PNG file"
# Render to image
"Render the topology to an image"
Customize Visualization
# Color customization
"Color router-1 red"
"Make all switches purple"
"Change the color of the firewalls to orange"
# Add labels
"Add labels to all devices"
"Label each device with its hostname"
# Highlighting
"Highlight router-1"
"Make core-rtr-01 stand out"
Scene Management
# Clear scene
"Clear the Blender scene"
"Reset the 3D view"
# Query scene
"What objects are in the Blender scene?"
"List the devices in Blender"
Device Color Mapping
| Device Type |
Color |
RGB |
| Router |
Blue |
(0.2, 0.4, 0.8) |
| Switch |
Green |
(0.2, 0.7, 0.3) |
| Firewall |
Red |
(0.8, 0.2, 0.2) |
| Access Point |
Yellow |
(0.9, 0.8, 0.2) |
| Unknown |
Gray |
(0.5, 0.5, 0.5) |
Device types are inferred from hostnames:
- Contains "rtr" or "router" → Router
- Contains "sw" or "switch" → Switch
- Contains "fw" or "firewall" or "asa" → Firewall
- Contains "ap" or "wap" or "wireless" → Access Point
Integration with Other Skills
- pyats-run: Query CDP/LLDP neighbor data from live devices
- suzieq-show: Query network state from SuzieQ observability platform
- canvas-a2ui: Alternative 2D visualization in chat
Error Handling
| Error Code |
Meaning |
Resolution |
| CONNECTION_FAILED |
Blender not running or addon not connected |
Start Blender, click 'Connect to Claude' in BlenderMCP panel |
| ADDON_NOT_READY |
Addon not connected |
Press 'N' in Blender, find BlenderMCP tab, click 'Connect' |
| NO_CDP_DATA |
No neighbor data available |
Query network devices first via pyats-run or suzieq-show |
| TIMEOUT |
First command may timeout |
This is normal - retry the same command |
| EXPORT_FAILED |
Export failed (window minimized) |
Ensure Blender window is visible |
Notes
- Read-only operations - no ServiceNow CR gating required
- Maximum 25 devices rendered per topology (performance limit)
- First command may timeout - subsequent commands are faster
- Requires Windows running Blender (WSL connectivity to Windows host)
- All operations logged to GAIT audit trail
1---
2name: blender-3d-viz
3description: "Create 3D network topology visualizations in Blender from CDP/LLDP neighbor data"
4license: Apache-2.0
5user-invocable: true
6metadata:
7 openclaw:
8 requires:
9 bins: ["python3", "uvx"]
10 env: ["BLENDER_HOST"]
11---
12
13# Blender 3D Network Visualization
14
15Create stunning 3D network topology visualizations in Blender from CDP/LLDP neighbor data. Network engineers can request topology drawings via natural language, and NetClaw translates neighbor discovery data into 3D rendering commands.
16
17## When to Use
18
19- Visualizing network topology in 3D for presentations
20- Creating topology diagrams from CDP/LLDP neighbor data
21- Exporting network diagrams as PNG images
22- Customizing device colors and adding labels
23- Demonstrating network architecture to stakeholders
24
25## MCP Server
26
27- **Server**: `blender-mcp` (community MCP via uvx)
28- **Command**: `uvx blender-mcp` (stdio transport)
29- **Host**: Windows running Blender with BlenderMCP addon (port 9876)
30- **Requirements**: Blender 3.0+, BlenderMCP addon installed and connected
31
32## Available Tools
33
34| Tool | Parameters | What It Does |
35|------|------------|--------------|
36| `get_scene_info` | None | Returns current Blender scene objects |
37| `create_object` | type, name, location, scale | Creates primitives (cube, sphere, cylinder) |
38| `modify_object` | name, position?, rotation?, scale? | Transform position/rotation/scale |
39| `set_material` | object_name, color, metallic?, roughness? | Apply colors and materials |
40| `execute_blender_code` | code | Run arbitrary Python in Blender |
41
42## Workflow Examples
43
44### Draw Network Topology
45
46```bash
47# Draw topology from CDP/LLDP data
48"Draw the network topology in Blender using CDP data"
49
50# Visualize neighbors for a specific device
51"Visualize the CDP neighbors for core-rtr-01 in 3D"
52
53# Create diagram from LLDP data
54"Create a 3D network diagram from the LLDP data"
55
56# Quick topology request
57"Show me the network topology in Blender"
58```
59
60### Export Visualization
61
62```bash
63# Export as PNG
64"Export the Blender scene as topology.png"
65
66# Save the diagram
67"Save the network diagram as a PNG file"
68
69# Render to image
70"Render the topology to an image"
71```
72
73### Customize Visualization
74
75```bash
76# Color customization
77"Color router-1 red"
78"Make all switches purple"
79"Change the color of the firewalls to orange"
80
81# Add labels
82"Add labels to all devices"
83"Label each device with its hostname"
84
85# Highlighting
86"Highlight router-1"
87"Make core-rtr-01 stand out"
88```
89
90### Scene Management
91
92```bash
93# Clear scene
94"Clear the Blender scene"
95"Reset the 3D view"
96
97# Query scene
98"What objects are in the Blender scene?"
99"List the devices in Blender"
100```
101
102## Device Color Mapping
103
104| Device Type | Color | RGB |
105|-------------|-------|-----|
106| Router | Blue | (0.2, 0.4, 0.8) |
107| Switch | Green | (0.2, 0.7, 0.3) |
108| Firewall | Red | (0.8, 0.2, 0.2) |
109| Access Point | Yellow | (0.9, 0.8, 0.2) |
110| Unknown | Gray | (0.5, 0.5, 0.5) |
111
112Device types are inferred from hostnames:
113- Contains "rtr" or "router" → Router
114- Contains "sw" or "switch" → Switch
115- Contains "fw" or "firewall" or "asa" → Firewall
116- Contains "ap" or "wap" or "wireless" → Access Point
117
118## Integration with Other Skills
119
120- **pyats-run**: Query CDP/LLDP neighbor data from live devices
121- **suzieq-show**: Query network state from SuzieQ observability platform
122- **canvas-a2ui**: Alternative 2D visualization in chat
123
124## Error Handling
125
126| Error Code | Meaning | Resolution |
127|------------|---------|------------|
128| CONNECTION_FAILED | Blender not running or addon not connected | Start Blender, click 'Connect to Claude' in BlenderMCP panel |
129| ADDON_NOT_READY | Addon not connected | Press 'N' in Blender, find BlenderMCP tab, click 'Connect' |
130| NO_CDP_DATA | No neighbor data available | Query network devices first via pyats-run or suzieq-show |
131| TIMEOUT | First command may timeout | This is normal - retry the same command |
132| EXPORT_FAILED | Export failed (window minimized) | Ensure Blender window is visible |
133
134## Notes
135
136- Read-only operations - no ServiceNow CR gating required
137- Maximum 25 devices rendered per topology (performance limit)
138- First command may timeout - subsequent commands are faster
139- Requires Windows running Blender (WSL connectivity to Windows host)
140- All operations logged to GAIT audit trail
gabrielmoreira