Skip to main content

Radarboard MCP server

Radarboard exposes its own built-in MCP server from the web app. This is the endpoint you use when connecting ChatGPT or another OAuth-capable MCP client to your Radarboard instance. This is separate from external MCP servers such as RevenueCat or OpenPanel that you configure in opencode.json.

Base URL

The MCP URL is derived from your deployed app URL:
If your app is deployed at:
your MCP server URL is:

Required environment variables

Set these on the web app deployment:
Generate a secret with:
NEXT_PUBLIC_APP_URL is the source of truth for the built-in MCP, OAuth, and discovery URLs.

Endpoints

How to verify

Once deployed, you can verify the MCP-related endpoints with:
The MCP endpoint itself requires a bearer token, so it will return 401 Unauthorized unless you call it with a valid OAuth-issued token.

Where to look in the codebase

If you need the implementation details:
  • apps/app/lib/env.ts defines the MCP-related env keys
  • apps/app/lib/mcp-oauth.ts reads NEXT_PUBLIC_APP_URL and RADARBOARD_API_SECRET
  • apps/app/app/api/mcp/route.ts exposes the built-in MCP endpoint
  • apps/app/app/.well-known/oauth-authorization-server/route.ts exposes OAuth server metadata
  • apps/app/app/.well-known/oauth-protected-resource/route.ts exposes protected resource metadata