Files
truenas-mcp/claude_desktop_config.example.json
Kris MooreandClaude Sonnet 4.5 37a75dc39c Refactor to single-binary architecture with direct TrueNAS WebSocket connection
Major architectural change from two-binary (server + proxy) to single native
binary that runs entirely on desktop and connects directly to TrueNAS.

Key changes:
- Single binary eliminates need for TrueNAS server deployment
- Direct WebSocket connection to TrueNAS middleware over wss://
- Security: Only allow wss:// connections (TrueNAS revokes API keys over ws://)
- Self-signed certificate support enabled by default
- MCP notification support (handles notifications/initialized)
- Simplified configuration: just hostname and API key
- Cross-platform builds: macOS (ARM64/AMD64), Linux, Windows

Architecture benefits:
- No deployment to TrueNAS required
- Runs entirely on user's desktop
- Simpler setup and configuration
- Better security with mandatory encryption
- Smaller codebase (~2000 lines of SSE code removed)

Co-Authored-By: Claude Sonnet 4.5 <noreply@anthropic.com>
2026-02-05 11:47:49 -05:00

12 lines
252 B
JSON

{
"mcpServers": {
"truenas": {
"command": "/usr/local/bin/truenas-mcp",
"args": [
"--truenas-url", "192.168.0.31",
"--api-key", "19-ZLHNjv0Hu0l8VwB9pXYQldIg2uCoLZzRaNhMyrZ47iYl1pE8RBvIBXs2N5Zdizsw"
]
}
}
}