Problem
Yavio ships an MCP server for the analytics platform itself — served by this deployment at /api/mcp — so you can query your own usage data from an MCP client. Nothing in the dashboard mentions it exists, so effectively nobody finds it.
Proposed Solution
A discreet pointer in the sidebar (bottom-left, near the user menu) linking to setup instructions with the server URL and connection steps.
The URL must not be hardcoded — it differs per deployment, and self-hosters need their own. mcpResourceUri() in lib/oauth/constants.ts:53 already returns exactly this (canonicalOrigin() + /api/mcp, resolved from NEXTAUTH_URL / APP_URL), so the sidebar should read from there rather than introduce a new setting.
Affected Package
Dashboard, Documentation
Problem
Yavio ships an MCP server for the analytics platform itself — served by this deployment at
/api/mcp— so you can query your own usage data from an MCP client. Nothing in the dashboard mentions it exists, so effectively nobody finds it.Proposed Solution
A discreet pointer in the sidebar (bottom-left, near the user menu) linking to setup instructions with the server URL and connection steps.
The URL must not be hardcoded — it differs per deployment, and self-hosters need their own.
mcpResourceUri()inlib/oauth/constants.ts:53already returns exactly this (canonicalOrigin()+/api/mcp, resolved fromNEXTAUTH_URL/APP_URL), so the sidebar should read from there rather than introduce a new setting.Affected Package
Dashboard, Documentation