# How the Blender MCP Server Handles Socket Timeouts (180‑Second Configuration)

> Discover how the Blender MCP server manages 180-second socket timeouts, invalidating connections and raising Python exceptions for unresponsive add-ons. Optimize your Blender workflow.

- Repository: [ahujasid/blender-mcp](https://github.com/ahujasid/blender-mcp)
- Tags: internals
- Published: 2026-04-13

---

**The Blender MCP server enforces a hard 180‑second timeout on all blocking socket operations, automatically invalidating connections and raising descriptive Python exceptions when the Blender add-on fails to respond within three minutes.**

The `ahujasid/blender-mcp` repository implements a Model Context Protocol (MCP) server that communicates with Blender via persistent TCP sockets. To prevent indefinite hangs during complex 3D operations, the server hardcodes a **180‑second timeout** (three minutes) across its networking layer in [`src/blender_mcp/server.py`](https://github.com/ahujasid/blender-mcp/blob/main/src/blender_mcp/server.py), ensuring robust