Mem · OAuth Scopes

Mem OAuth Scopes

OAuth 2.0 searched

Mem publishes 4 OAuth 2.0 scopes via the authorizationCode and clientCredentials flows. Scopes are the fine-grained permissions an application requests at authorization time to act against the Mem API on a user’s behalf.

Tokens are issued from https://api.mem.ai/api/v2/oauth2/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.

CompanyNotesKnowledge ManagementProductivityArtificial IntelligenceNote TakingSearchMCPAgentsMeetings

Scopes: 4 Flows: authorizationCode, clientCredentials Method: searched

OAuth endpoints

Authorization URL
https://mem.ai/oauth/consent

Token URL
https://api.mem.ai/api/v2/oauth2/token

Flows
authorizationCodeclientCredentials

Scopes (4)

Scope	Description	Flows
content.read	Read access to the user's Mem notes and collections.	authorizationCode, clientCredentials
content.write	Create, update, and organize the user's Mem notes and collections.	authorizationCode, clientCredentials
profile.read	Read access to the user's Mem profile.	authorizationCode
profile.write	Write access to the user's Mem profile.	authorizationCode

📄 Provider scope reference: https://docs.mem.ai/mcp/setup

Source

OAuth Scopes

generated: '2026-07-20'
method: searched
source: https://api.mem.ai/.well-known/oauth-authorization-server
docs: https://docs.mem.ai/mcp/setup
schemes:
  - name: OAuth2
    source: https://api.mem.ai/.well-known/oauth-authorization-server
    issuer: https://api.mem.ai
    flows:
      - flow: authorizationCode
        authorizationUrl: https://mem.ai/oauth/consent
        tokenUrl: https://api.mem.ai/api/v2/oauth2/token
        pkce: S256
      - flow: clientCredentials
        tokenUrl: https://api.mem.ai/api/v2/oauth2/token
    registration_endpoint: https://api.mem.ai/oauth2/register
    dynamic_client_registration: true
scopes:
  - scope: content.read
    description: Read access to the user's Mem notes and collections.
    flows: [authorizationCode, clientCredentials]
    sources: [well-known/mem-oauth-authorization-server.json, well-known/mem-oauth-protected-resource.json]
  - scope: content.write
    description: Create, update, and organize the user's Mem notes and collections.
    flows: [authorizationCode, clientCredentials]
    sources: [well-known/mem-oauth-authorization-server.json, well-known/mem-oauth-protected-resource.json]
  - scope: profile.read
    description: Read access to the user's Mem profile.
    flows: [authorizationCode]
    sources: [well-known/mem-openid-configuration.json]
  - scope: profile.write
    description: Write access to the user's Mem profile.
    flows: [authorizationCode]
    sources: [well-known/mem-openid-configuration.json]
notes: >-
  Scopes are advertised via OAuth 2.0 Authorization Server Metadata (RFC 8414)
  and OIDC discovery on api.mem.ai. The hosted MCP server (mcp.mem.ai) scopes
  its protected resource to content.read + content.write. The REST API's own
  OpenAPI securitySchemes declare bearer-token (API key) auth; OAuth 2.0 is the
  mechanism used for the MCP server and third-party app connectors.