internals

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

April 13, 2026 ahujasid/blender-mcp ↗

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, ensuring robust

Have a question about this repo?

These articles cover the highlights, but your codebase questions are specific. Give your agent direct access to the source. Share this with your agent to get started:

Share the following with your agent to get started:

curl -s "https://instagit.com/install.md"

Add to your MCP client configuration:

{
  "mcpServers": {
    "instagit": {
      "command": "npx",
      "args": ["-y", "instagit@latest"]
    }
  }
}

Ask your agent:

"Use Instagit MCP to understand how ahujasid/blender-mcp works."

Works with

Claude Codex Cursor VS Code OpenClaw Any MCP Client

Maintain an open-source project? Get it listed too →