Fix Datadog MCP endpoint fallback

[philjestin]

Summary

• Prefer healthy existing Datadog MCP servers, but fall back to a Boatman-managed boatman-datadog-mcp server when Claude's Datadog plugin is missing, unauthenticated, or configured with the legacy remote endpoint.
• Create the fallback server against Datadog's current /v1/mcp endpoint with the routine toolsets before opening the interactive Claude MCP login.
• Update routine docs and frontend test fixtures to describe the Boatman-managed Datadog MCP path.

Root Cause

The Datadog Claude plugin can point at the older /api/unstable/mcp-server/mcp remote endpoint. That OAuth flow can return invalid_request - Invalid client_id parameter value, even though Boatman successfully opened an interactive terminal for Claude MCP login.

Validation

• go test . ./agent/providers/claudecli from desktop
• npm run test:run -- src/components/routines/RoutineView.test.tsx from desktop/frontend
• npm run build from desktop/frontend
• make quality

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
boatmanmode	Ready	Preview, Comment	Jul 10, 2026 5:46pm