Accord · OAuth Scopes

Accord OAuth Scopes

OAuth 2.0 probed

Accord uses OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (e.g. client-credentials or role-based authorization) rather than per-scope consent.

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.

Sales EnablementRevenue OperationsCustomer CollaborationSales EngagementCustomer OnboardingMutual Action PlansCRMGraphQLMCPagent-nativeSaaSCompany

Scopes: 0 Flows: Method: probed

Scopes (0)

Accord implements OAuth 2.0 but publishes no discrete scopes — access is governed by the grant itself (client-credentials or role-based authorization) rather than per-scope consent.

Read from Accord's own RFC 8414 authorization-server metadata and RFC 9728 protected-resource metadata, both served anonymously on api.inaccord.com. These scopes govern the Accord MCP server. The Accord Developer API (GraphQL) does NOT use OAuth — it authenticates with a workspace-scoped bearer API key and has no scope surface; per Accord's authentication page, "the same Row-Level Security rules that apply to in-app sessions apply to API key requests". Accord publishes no separate scopes/permissions reference page; nothing beyond the metadata was found.

📄 Provider scope reference:

Source

OAuth Scopes

generated: '2026-09-06'
method: probed
source: https://api.inaccord.com/.well-known/oauth-authorization-server
name: Accord OAuth scopes
note: >-
  Read from Accord's own RFC 8414 authorization-server metadata and RFC 9728 protected-resource metadata, both served
  anonymously on api.inaccord.com. These scopes govern the Accord MCP server. The Accord Developer API (GraphQL) does
  NOT use OAuth — it authenticates with a workspace-scoped bearer API key and has no scope surface; per Accord's
  authentication page, "the same Row-Level Security rules that apply to in-app sessions apply to API key requests".
  Accord publishes no separate scopes/permissions reference page; nothing beyond the metadata was found.
docs: null
flows:
  - type: authorization_code
    authorization_endpoint: https://api.inaccord.com/1/mcp/authorize
    token_endpoint: https://api.inaccord.com/1/mcp/token
    pkce_required: true
    code_challenge_methods:
      - S256
  - type: refresh_token
    token_endpoint: https://api.inaccord.com/1/mcp/token
scope_count: 2
scopes:
  - name: mcp:read
    description: >-
      Read access through the Accord MCP server. Advertised in both the authorization-server and protected-resource
      metadata. Accord documents the server as read-only in beta, so this is the scope in use today. No per-scope
      description is published by Accord; this note records what the documentation states, not an inferred meaning.
  - name: mcp:write
    description: >-
      Write access through the Accord MCP server. Advertised in the metadata, but Accord's announcement states the
      server "currently reads from your Accord workspace" with write support planned, so this scope is declared ahead
      of the capability. No per-scope description is published by Accord.

Work with this as data

Every scope set here is available over the APIs.io API and to AI agents over MCP.

MCP server

One button, every client — Claude, Cursor, VS Code and the rest.

https://apis.io/mcp

Tools for oauth scopes

4 MCP tools reach this

find_scopesBrowse and filter every scope set in the catalog.
apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.
resolveTurn a domain, URL or GitHub org into the provider it belongs to.
find_cohortsEvery scored population of providers in the catalog.

All 92 tools →

Call it yourself

curl for this page

This scope set

curl "https://apis.io/api/v1/scopes/accordacff-scopes"

All oauth scopes

curl "https://apis.io/api/v1/scopes?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

Get an API key

Free tier, no email required.

GitHub Google LinkedIn

A second provider on the same verified email joins the account you already have.