Skip to main content

I used to build websites. Now I build what builds them.

I’m Tim Benniks, Developer Experience and Product Leader at Contentstack. I build developer tools and write about AI engineering, composable architecture, and what makes software useful.

Sketched portrait of Tim Benniks

The journal

Recent writing

Essays on developer experience, AI-accelerated engineering, and the platforms that hold it all up.

Sep 4, 20267 min read

Building MCP Profile Hub part 2, one MCP server is the wrong abstraction

This article argues that a single, monolithic MCP server per platform is the wrong abstraction, especially for complex systems like Contentstack. Instead, it introduces managed profiles as the right unit of configuration, aligned to jobs, teams, or access boundaries rather than product catalogs. Each managed profile bundles a curated set of tools, Automations, and agents, enriched with account context, while still respecting individual user identities and permissions. Profiles can only narrow what a user can do, never expand their underlying platform permissions. This makes configurations easier to reason about, review, audit, and replicate across environments, and offers a scalable pattern for enterprise platforms with many roles and capabilities.

Aug 31, 20269 min read

Building MCP Profile Hub, part 1: Stop making the agent ask

Introducing MCP Profile Hub. I explain why enriching tool definitions with tenant-specific context dramatically improves agent performance. Instead of exposing generic CMS tools that force models to discover content types, environments, locales, and branches through multiple lookup calls, Profile Hub injects real account data directly into JSON Schemas as enums, defaults, and descriptions. This reduces tool calls, latency, and reasoning tokens while avoiding misleading examples and invalid defaults. The piece also covers the production engineering behind enrichment, how Automations and Agent OS agents are exposed as high-level deterministic tools, and why reusable HTTP-based tool definitions let teams run their own MCP runtimes. The core takeaway is that fewer, richer, context-aware tools beat large generic catalogs for real-world agent workflows.

  • Composable architecture
  • AI engineering
  • API design
Aug 24, 20267 min read

Claude Desktop MCP lifecycle is broken

Claude Desktop currently launches duplicate local MCP stdio servers for a single configuration, causing two independent OAuth flows, extra browser tabs, and unnecessary resource usage. The bug is masked once credentials are cached, so it silently persists in production while still spawning two processes every time. This is not an mcp-remote or external service issue but a host-level lifecycle problem, likely caused by overlapping legacy and new MCP managers and poor observability for one of the processes. Workarounds like pre-authenticating with mcp-remote mitigate UX pain but do not fix the duplication. The article argues that open-source tools should not shoulder complex coordination logic just to survive a major desktop app’s sloppy process management.

  • Composable architecture
  • AI engineering
  • Performance

The workbench

What I'm building

Agentlint, platform SDKs, local-first Mac apps, and the occasional weekend experiment. Real code, real trade-offs, work in progress.

The short version

More about Tim

Tim Benniks

Twenty years building digital platforms for global brands. Now leading Developer Experience at Contentstack, shaping the future of developer-facing products and AI-driven workflows.

Tim Benniks is a Developer Experience and Product leader at Contentstack, where he drives DX, Developer Hub & Marketplace, MCP, and Agent Skills. Tim is a frequent speaker, content creator, ambassador for Cloudinary, Supabase, Nuxt, Algolia and Co-chair of the Enterprise AI Agents Workgroup at the MACH Alliance.

When output is cheap, taste is everything.

AI makes it easier to build. Choosing what deserves to exist still takes judgment, curiosity, and a rested mind.

Got a stage, a podcast, or a developer team that needs sharpening? Let's talk.