Serval · OAuth Scopes

Serval OAuth Scopes

OAuth 2.0 searched

Serval publishes 1 OAuth 2.0 scope via the authorizationCode flow. Scopes are the fine-grained permissions an application requests at authorization time to act against the Serval API on a user’s behalf.

Tokens are issued from https://public.api.serval.com/oauth/token.

This index is generated from the provider’s OpenAPI security definitions (and, where available, its documented scope reference) and refreshes on every APIs.io network build. Browse every provider’s scopes at scopes.apis.io.

CompanyIT Service ManagementITSMHelp DeskWorkflow AutomationAI AgentsAccess ManagementEmployee SupportTicketing

Scopes: 1 Flows: authorizationCode Method: searched

OAuth endpoints

Authorization URL
https://public.api.serval.com/oauth/authorize

Token URL
https://public.api.serval.com/oauth/token

Flows
authorizationCode

Scopes (1)

Scope	Description	Flows
serval:user	Act on behalf of an authenticated Serval user through the OAuth authorization server (the scope requested by the hosted MCP server / delegated agent clients). This is the only scope advertised in the RFC 8414 authorization-server metadata (scopes_supported: ["serval:user"]).	authorizationCode

📄 Provider scope reference: https://docs.serval.com/sections/documentation/end-user/mcp-quickstart

Source

OAuth Scopes

generated: '2026-07-21'
method: searched
source: https://public.api.serval.com/.well-known/oauth-authorization-server
docs: https://docs.serval.com/sections/documentation/end-user/mcp-quickstart
schemes:
  - name: OAuth2
    source: well-known/serval-oauth-authorization-server.json
    flows:
      - flow: authorizationCode
        authorizationUrl: https://public.api.serval.com/oauth/authorize
        tokenUrl: https://public.api.serval.com/oauth/token
        pkce: S256
scopes:
  - scope: serval:user
    description: >
      Act on behalf of an authenticated Serval user through the OAuth authorization server
      (the scope requested by the hosted MCP server / delegated agent clients). This is the
      only scope advertised in the RFC 8414 authorization-server metadata
      (scopes_supported: ["serval:user"]).
    flows: [authorizationCode]
    sources: [well-known/serval-oauth-authorization-server.json]
notes: >
  Serval's public REST API (/v2/*) does not use OAuth scopes — it uses a Basic
  client_id:client_secret -> Bearer token exchange (see authentication/). The scope
  surface here belongs to the separate OAuth 2.0 authorization server used by the MCP
  server and interactive agent clients. Per-team API access is scoped by the admin at
  integration setup time rather than via OAuth scopes.