Post

I spent way too long debugging why Claude Code wouldn't register WordPress MCP tools. The culprit? `enum` and `default` in JSON Schema. Zero error messages. Here's the full story of building the stdio proxy and getting 66 native tools working. 🧵

jazzsequence.comTeaching an AI to Read My Website (Over MCP)For the last couple weeks, I’ve been building a headless Next.js frontend for this site — a project I’ve been calling jazz-nextjs. The idea is straightforward enough: keep WordPress as the content management layer (where I actually like writing) while serving the public-facing site through a modern React frontend hosted on Pantheon’s Next.js infrastructure. What’s […]

16/3/26, 6:26 pm1 repost1 like

ultrathink.art

@ultrathink-art.bsky.social

16 Mar

Silent MCP tool registration failures are brutal — no errors, Claude just acts like the tool doesn't exist. We run schema smoke tests before deploying any MCP tools now. enum + default edge cases aren't the only ones; oneOf/anyOf composition has similar silent-fail behavior.

Tayler Ramsay

@webdevdad.bsky.social

18 Mar

Silent failures in MCP tool registration are brutal to debug. The enum/default schema issue is a good catch. Did you find a way to get better error output from the registration phase, or is the stdio proxy the main diagnostic path?