Synup · OAuth Scopes

Synup OAuth Scopes

OAuth 2.0 probed

Synup publishes 2 OAuth 2.0 scopes. Scopes are the fine-grained permissions an application requests at authorization time to act against the Synup API on a user’s behalf.

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.

Local MarketingListings ManagementReputation ManagementLocal SEOReviewsSocial-MediaAnalyticsBusiness ListingsReview ManagementAgency Software

Scopes: 2 Flows: Method: probed

Scopes (2)

Scope	Description	Flows
mcp:read	Read-only access to the Synup MCP tool surface: look up locations, reviews, rankings, listings, analytics. Equivalent to X-access-mode: read for key-authenticated sessions.
mcp:write	Create, update and delete through the Synup MCP tool surface. Equivalent to X-access-mode: write. Synup guidance is to start in read and switch to write deliberately.

📄 Provider scope reference: https://developer.synup.com/synup-mcp-getting-connected-doc-2070739

Source

OAuth Scopes

name: Synup OAuth scopes
generated: '2026-08-13'
method: probed
source: https://mcp-agent.synup.com/.well-known/oauth-authorization-server
docs: https://developer.synup.com/synup-mcp-getting-connected-doc-2070739
description: The only OAuth surface Synup publishes is the MCP server. Its authorization-server metadata
  declares two coarse scopes. The REST API v4 has no OAuth and therefore no scopes — it is API-key authenticated.
issuer: https://mcp-agent.synup.com
applies_to: https://mcp-agent.synup.com/mcp (and every tenant workspace domain + /mcp)
scope_count: 2
scopes:
- scope: mcp:read
  description: 'Read-only access to the Synup MCP tool surface: look up locations, reviews, rankings,
    listings, analytics. Equivalent to X-access-mode: read for key-authenticated sessions.'
- scope: mcp:write
  description: 'Create, update and delete through the Synup MCP tool surface. Equivalent to X-access-mode:
    write. Synup guidance is to start in read and switch to write deliberately.'
granularity: coarse
notes:
- Both scopes were read from the live RFC 8414 document and confirmed in the WWW-Authenticate challenge
  on an anonymous tools/list call (scope="mcp:read mcp:write").
- There is no per-domain or per-resource scope; the X-tags-include/X-tags-exclude headers narrow which
  tools are surfaced but are not an authorization boundary.
- REST API v4 keys are unscoped — see authentication/synup-authentication.yml.

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/synup-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.