Gojiberry AI · OAuth Scopes

Gojiberry AI OAuth Scopes

OAuth 2.0 probed

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

Tokens are issued from https://mcp.gojiberry.ai/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.

CompanySalesLead GenerationSales IntelligenceAI AgentsOutboundGo-To-MarketProspectingLinkedInCRM

Scopes: 2 Flows: authorizationCode Method: probed

OAuth endpoints

Authorization URL
https://mcp.gojiberry.ai/authorize

Token URL
https://mcp.gojiberry.ai/token

Flows
authorizationCode

Scopes (2)

Scope	Description	Flows
mcp:tools	Advertised scope granting an MCP client access to the Gojiberry tool surface. No published description; name read from scopes_supported.	authorizationCode
claudeai	Advertised scope used by the Claude MCP connector flow documented at https://gojiberry.ai/how-to-do-outreach-claude-linkedin-mcp. No published description; name read from scopes_supported.	authorizationCode

📄 Provider scope reference:

Source

OAuth Scopes

generated: '2026-08-13'
method: probed
source: https://mcp.gojiberry.ai/.well-known/oauth-authorization-server
note: >-
  The External REST API at ext.gojiberry.ai has NO OAuth surface — it is a
  bearer API key (JWT) only, so derive-oauth-scopes.py finds zero oauth2
  securitySchemes in the OpenAPI. The OAuth scopes recorded here belong to the
  hosted MCP server at mcp.gojiberry.ai, which publishes RFC 8414 authorization
  server metadata and RFC 9728 protected resource metadata anonymously. Gojiberry
  publishes no human-readable scope reference page; these values are read
  verbatim from the machine-readable metadata.
schemes:
- name: MCP OAuth 2.1
  surface: mcp
  source: well-known/gojiberry-ai-oauth-authorization-server.json
  issuer: https://mcp.gojiberry.ai
  dynamic_client_registration: https://mcp.gojiberry.ai/register  # RFC 7591
  flows:
  - flow: authorizationCode
    authorizationUrl: https://mcp.gojiberry.ai/authorize
    tokenUrl: https://mcp.gojiberry.ai/token
    pkce: [S256, plain]
    grant_types: [authorization_code, refresh_token]
    token_endpoint_auth_methods: [none, client_secret_post]
scopes:
- scope: mcp:tools
  description: >-
    Advertised scope granting an MCP client access to the Gojiberry tool
    surface. No published description; name read from scopes_supported.
  flows: [authorizationCode]
  sources: [well-known/gojiberry-ai-oauth-authorization-server.json]
- scope: claudeai
  description: >-
    Advertised scope used by the Claude MCP connector flow documented at
    https://gojiberry.ai/how-to-do-outreach-claude-linkedin-mcp. No published
    description; name read from scopes_supported.
  flows: [authorizationCode]
  sources: [well-known/gojiberry-ai-oauth-authorization-server.json]
gaps:
- No scopes/permissions reference page is published on the docs site.
- The REST External API has no scope model; access is all-or-nothing per API key,
  with organization-owner impersonation via x-impersonate-user-id.