SocialBee · OAuth Scopes

SocialBee OAuth Scopes

OAuth 2.0 probed

SocialBee 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.

Social Media ManagementContent SchedulingContent RecyclingSocial Media AnalyticsAI Caption GenerationSocial Media PublishingMCPMarketing AutomationSoftware-as-a-Service

Scopes: 0 Flows: Method: probed

Scopes (0)

SocialBee 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.

📄 Provider scope reference:

Source

OAuth Scopes

generated: '2026-08-13'
method: probed
source: https://socialbee.com/.well-known/oauth-authorization-server
name: SocialBee OAuth Scopes
description: >-
  The complete published scope vocabulary for SocialBee's OAuth 2.1 authorization
  server. Both the RFC 8414 authorization server metadata and the RFC 9728
  protected resource metadata declare a single scope, "mcp". There is no scopes
  or permissions reference page — SocialBee does not document this authorization
  server at all, so the metadata document is the only source.
docs: null

scopes:
  - name: mcp
    description: >-
      The only scope advertised by the authorization server. Grants access to the
      Model Context Protocol server at
      https://socialbee.com/wp-json/mcp/mcp-oauth-server. No finer-grained
      scope vocabulary is published, so this is an all-or-nothing grant for the
      MCP resource.
    source: metadata
    resource: https://socialbee.com/wp-json/mcp/mcp-oauth-server

granularity:
  level: coarse
  read_write_split: false
  resource_scoped: false
  note: >-
    A single opaque scope with no read/write or per-resource separation. An agent
    cannot request least privilege: consenting to "mcp" consents to whatever the
    server's full tool set does. Whether that set is read-only cannot be
    determined without an authenticated tools/list.

summary:
  scope_count: 1
  source_of_truth: RFC 8414 authorization server metadata
  documented_by_provider: false

x-evidence:
  fetched: '2026-08-13'
  probes:
    - url: https://socialbee.com/.well-known/oauth-authorization-server
      http_status: 200
      field: scopes_supported
      value: ["mcp"]
    - url: https://socialbee.com/.well-known/oauth-protected-resource
      http_status: 200
      field: scopes_supported
      value: ["mcp"]

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/socialbee-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 form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.

GitHub Google LinkedIn

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