tRPC router
oauth
The dancer's side of connected apps (MCP): the /oauth/authorize consent screen and /settings/connections. Web sessions only: none of these paths is in server/trpc/scopes.ts, so an app's token can never call them (an app can't approve its own consent or list other connections).
Procedures (6)
Input
{
response_type?: string // len 0..40
client_id?: string // len 0..500
redirect_uri?: string // len 0..2000
code_challenge?: string // len 0..200
code_challenge_method?: string // len 0..20
state?: string // len 0..2000
scope?: string // len 0..1000
resource?: string // len 0..500
}Input
{
requestToken: string // len 10..4096
scopes: string[] // items 0..20
profileIds?: string[] // items 0..100, default []
}Input
{
requestToken: string // len 10..4096
}Tables
None (no database access).
Input
void
Input
{
id: string // uuid
}Tables
Input
{
username: string // len 1..200
}Source: server/trpc/routers/oauth.ts