Fix MCP “No tools, prompts or resources” in Cursor

[Harshul23]

Summary

• add server-level diagnostics (stdio error hooks, uncaught exception handlers) so Cursor can surface initialization failures
• harden shadcn mcp bootstrap: explicit logging for each startup phase, exit non‑zero on failures, and better tool registration validation.
• emit debug breadcrumbs for every tool request to make Cursor’s MCP inspector useful for support teams

Testing

• pnpm --filter shadcn build
• node packages/shadcn/dist/index.js mcp (manual: verify logs show tool registration and tool calls)
• Cursor MCP panel now lists 7 tools instead of “No tools, prompts or resources” (confirmed via local stdio logs)

Notes

• Root cause tracked in #8843 Cursor fails silently when the stdio MCP process doesn’t log errors. These changes give Cursor enough signal to report failures and keep the tool list populated.

closes #8843

[vercel]

@Harshul23 is attempting to deploy a commit to the shadcn-pro Team on Vercel.

A member of the Team first needs to authorize it.