Meltwater · OAuth Scopes

Meltwater OAuth Scopes

OAuth 2.0 probed

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

Tokens are issued from https://app.meltwater.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.

Media MonitoringSocial ListeningPR AnalyticsBrand IntelligenceNews APISocial AnalyticsMedia Intelligence

Scopes: 5 Flows: authorizationCode Method: probed

OAuth endpoints

Authorization URL
https://app.meltwater.com/oauth/authorize

Token URL
https://app.meltwater.com/oauth/token

Flows
authorizationCode

Scopes (5)

Scope	Description	Flows
tools:read	List the MCP tools exposed to the caller's Meltwater package.	authorizationCode
tools:call	Invoke an MCP tool against the caller's Meltwater assets and data.	authorizationCode
openid	OpenID Connect authentication scope advertised by the authorization server.	authorizationCode
profile	Profile claims.	authorizationCode
email	Email claim.	authorizationCode

📄 Provider scope reference: https://developer.meltwater.com/guides/meltwater-mcp/connecting

Source

OAuth Scopes

generated: '2026-08-13'
method: probed
source: https://api.meltwater.com/.well-known/oauth-protected-resource
docs: https://developer.meltwater.com/guides/meltwater-mcp/connecting
note: >-
  The OpenAPI declares only an apiKey scheme, so nothing scope-shaped is derivable from the
  specs. The scopes below were read from Meltwater's own live OAuth discovery documents
  (RFC 9728 protected-resource metadata on api.meltwater.com, RFC 8414 authorization-server
  metadata on app.meltwater.com), which are already served even though the MCP connecting
  guide still describes OAuth 2.0 as "planned for later this year".
authorization_server: https://app.meltwater.com
protected_resource: https://api.meltwater.com/v2/mcp
schemes:
  - name: oauth2
    source: https://app.meltwater.com/.well-known/oauth-authorization-server
    flows:
      - flow: authorizationCode
        authorizationUrl: https://app.meltwater.com/oauth/authorize
        tokenUrl: https://app.meltwater.com/oauth/token
        pkce: [S256]
    registration_endpoint: https://app.meltwater.com/oauth/register
    revocation_endpoint: https://app.meltwater.com/oauth/revoke
    grant_types: [authorization_code, refresh_token]
    token_endpoint_auth_methods: [none, client_secret_post, client_secret_basic]
scopes:
  - scope: tools:read
    description: List the MCP tools exposed to the caller's Meltwater package.
    flows: [authorizationCode]
    sources: ['https://api.meltwater.com/.well-known/oauth-protected-resource', 'https://app.meltwater.com/.well-known/oauth-authorization-server']
  - scope: tools:call
    description: Invoke an MCP tool against the caller's Meltwater assets and data.
    flows: [authorizationCode]
    sources: ['https://api.meltwater.com/.well-known/oauth-protected-resource', 'https://app.meltwater.com/.well-known/oauth-authorization-server']
  - scope: openid
    description: OpenID Connect authentication scope advertised by the authorization server.
    flows: [authorizationCode]
    sources: ['https://app.meltwater.com/.well-known/oauth-authorization-server']
  - scope: profile
    description: Profile claims.
    flows: [authorizationCode]
    sources: ['https://app.meltwater.com/.well-known/oauth-authorization-server']
  - scope: email
    description: Email claim.
    flows: [authorizationCode]
    sources: ['https://app.meltwater.com/.well-known/oauth-authorization-server']
x-evidence:
  - url: https://api.meltwater.com/.well-known/oauth-protected-resource
    status: 200
  - url: https://app.meltwater.com/.well-known/oauth-authorization-server
    status: 200