generated: '2026-08-29'
method: probed
source: https://agent.ec-force.com/.well-known/oauth-authorization-server
docs: https://ec-force.com/information/20260804
note: >-
  Read directly from the ecforce AI MCP authorization server's RFC 8414 metadata, which is served
  anonymously. The server advertises exactly one scope. No scopes/permissions reference page is
  published — the ecforce v2 REST API uses a member-permission model configured per API connection
  user in the admin screens rather than OAuth scopes, and that configuration is behind the tenant
  login. derive-oauth-scopes.py was not applicable: there is no OpenAPI in this repo to derive from.
authorization_server: https://agent.ec-force.com
flows:
- type: authorization_code
  authorization_url: https://agent.ec-force.com/mcp/oauth/authorize
  token_url: https://agent.ec-force.com/mcp/oauth/token
  refresh_supported: true
  pkce: S256
  dynamic_client_registration: https://agent.ec-force.com/mcp/oauth/register
scopes:
- name: mcp
  description: >-
    The single scope advertised by the ecforce AI MCP authorization server. Effective authority is
    not carried in the scope string: the provider states access is bounded by the ecforce services
    the tenant has contracted and by the signed-in ecforce account's own permission scope, so two
    tokens carrying "mcp" can reach different data.
  source: oauth-authorization-server metadata
scope_count: 1