ngLover

Last week at SIGGRAPH 2026 in Los Angeles, six major professional creative applications announced Model Context Protocol server integrations at the same conference. Blender, Unreal Engine, Adobe Creative Cloud, SideFX Houdini 22, Boris FX Silhouette, and Foundry Griptape. Not demos or research previews. Announced and demonstrated, shipping or in active preview. That is the story. The protocol that started in AI coding assistants just crossed into the professional DCC (digital content creation) ecosystem all at once. If you have been building with MCP on the AI tooling side, this should get your attention. Not because Blender and Houdini suddenly matter to your agent pipeline, but because of what it means when a standard connection layer starts showing up in professional software categories at scale. What Each Integration Actually Does Let me be concrete, because the announcement headline does not tell you much on its own. Unreal Engine now exposes editor capabilities through an M...

If you're building AI agent workflows, n8n is no longer just a "webhook plus HTTP node" automation tool. As of late 2025, it has native Model Context Protocol support on both ends: it can call external MCP servers and expose its own workflows as MCP tools. That changes how you think about connecting AI agents to automation. Here are the three distinct ways you can wire n8n and MCP together, and where each one actually fits. Why MCP Matters for n8n Developers MCP (Model Context Protocol) , open-sourced by Anthropic in late 2024, became the de facto standard for AI-to-tool communication through 2025. The idea is simple: instead of hardcoding tool schemas into every AI app, you expose them through a standard JSON-RPC interface over SSE or streamable HTTP. Any MCP-compatible client, Claude, GPT-4o, Cursor, Windsurf, can discover and call those tools without custom integration code. n8n added two nodes that put it on both sides of this equation. The community announcement...

The Model Context Protocol's next specification — release candidate locked May 21, 2026, final spec shipping July 28 — is the most significant protocol revision since MCP launched. If you're running MCP servers in any production context, the headline change is architectural: the stateful session layer is gone. I've been tracking the SEPs (Specification Enhancement Proposals) that make up this release. Here's the breakdown of what's actually changing and what you need to do before July 28. The Big Change: MCP Is Now Stateless The current spec requires an initialize / initialized handshake and tracks sessions via Mcp-Session-Id . That means sticky routing — every request mid-session must hit the same server instance that handled the handshake. For anyone running more than one server instance behind a load balancer, this has meant either session affinity configs, shared session stores, or both. The July 2026 spec eliminates all of that. No session handshake. No s...

If You're Running OpenClaw, You May Want to Read This A public watchboard has surfaced listing over 250,000 OpenClaw instances that are directly reachable from the internet. Some of these instances have leaked credentials. Many are running on infrastructure already flagged for known CVEs and threat actor activity. This isn't theoretical. It's happening right now. You can check the exposure list yourself at openclaw.allegro.earth . Why This Is a Big Deal OpenClaw is a powerful AI agent framework. That power comes with serious responsibility. A typical OpenClaw deployment runs with: Personal API keys — OpenAI, Anthropic, Google, cloud provider credentials Broad system permissions — file access, shell execution, network requests Autonomous execution capabilities — the agent can act without human approval Complex codebases — large attack surfaces that haven't been fully audited When one of these instances is publicly reachable without authentication...

Prompt engineering isn't completely dead. If you're summarizing emails or classifying support tickets, a well-written system prompt still gets you 90% of the way there. But if you're building agents, and most of us are building agents now, prompt engineering is the wrong mental model. It's not the bottleneck anymore. The system around the model is. What Prompt Engineering Actually Was From 2022 to 2024, most AI work was "how do I phrase this to get better output." Few-shot examples, chain-of-thought prompting, temperature tuning. The skill was about poking a stateless model and getting a useful single-turn response. That made sense when models were barely reliable and the main interface was a text completion box. The best prompt engineers I knew were essentially UX designers for language models. The craft was real. But it was always a workaround for a gap between what models could do and what they needed to do. As models improved and workflows got mor...