Kagura AI

Kagura AI Well Known API

OAuth2 discovery endpoints

GitHub OpenAPI

Operations 5

GET /.well-known/oauth-protected-resource/mcp Oauth Protected Resource Mcp #
GET /.well-known/oauth-protected-resource Oauth Protected Resource #
GET /.well-known/openid-configuration Openid Configuration #
GET /.well-known/oauth-authorization-server Oauth Authorization Server #
GET /.well-known/google-connected-apps Google Connected Apps Verification #

Specifications

⚙
OpenAPI
https://artifacts.apis.io/kagura-ai-com/openapi/kagura-ai-com-well-known-api-openapi.yml

Schemas & Data

📊
JSONSchema
https://artifacts.apis.io/kagura-ai-com/json-schema/kagura-ai-com-context-search-config-response-schema.json
📊
JSONSchema
https://artifacts.apis.io/kagura-ai-com/json-schema/kagura-ai-com-remember-request-schema.json
📊
JSONSchema
https://artifacts.apis.io/kagura-ai-com/json-schema/kagura-ai-com-context-search-config-update-schema.json
📊
JSONSchema
https://artifacts.apis.io/kagura-ai-com/json-schema/kagura-ai-com-plan-tier-feature-schema.json
📊
JSONSchema
https://artifacts.apis.io/kagura-ai-com/json-schema/kagura-ai-com-patch-memory-request-schema.json
📊
JSONSchema
https://artifacts.apis.io/kagura-ai-com/json-schema/kagura-ai-com-workspace-connector-create-request-schema.json

Work with this as data

Every API 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 apis

7 MCP tools reach this
  • find_apisBrowse and filter every API in the catalog.
  • get_api_artifactsOne API's artifacts, grouped by type.
  • get_openapiThe primary OpenAPI for this API.
  • find_similar_apisAPIs that look like this one.
  • 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 API 
curl "https://apis.io/api/v1/apis/kagura-ai-com:kagura-ai-com-well-known-api"
All apis 
curl "https://apis.io/api/v1/apis?limit=25"

Calls without X-API-Key need no key. Calls with it need a paid plan — get a key.

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.

OpenAPI Specification

kagura-ai-com-well-known-api-openapi.yml Raw ↑ 
openapi: 3.2.0
info:
  title: Kagura Memory Cloud Well Known API
  description: Universal AI Memory Platform - Remote MCP Server + Web Management
  version: 0.158.1
tags:
- name: .well Known
  description: OAuth2 discovery endpoints
paths:
  /.well-known/oauth-protected-resource/mcp:
    get:
      tags:
      - .well Known
      summary: Oauth Protected Resource Mcp
      description: 'OAuth 2.0 Protected Resource Metadata for /mcp endpoint.


        Claude Desktop may request resource-specific metadata.

        Redirects to main oauth-protected-resource endpoint.'
      operationId: oauth_protected_resource_mcp__well_known_oauth_protected_resource_mcp_get
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
  /.well-known/oauth-protected-resource:
    get:
      tags:
      - .well Known
      summary: Oauth Protected Resource
      description: 'OAuth 2.0 Protected Resource Metadata.


        Required by OpenAI Apps SDK for ChatGPT integration.


        Spec: RFC 8707 - Resource Indicators for OAuth 2.0

        https://datatracker.ietf.workspace/doc/html/rfc8707


        Returns:

        Protected resource metadata'
      operationId: oauth_protected_resource__well_known_oauth_protected_resource_get
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
  /.well-known/openid-configuration:
    get:
      tags:
      - .well Known
      summary: Openid Configuration
      description: 'OpenID Connect Discovery 1.0 Metadata.


        Required by MCP clients (Claude Desktop, Claude Code) per MCP Authorization

        specification (June 2025 revision).


        Spec: OpenID Connect Discovery 1.0

        https://openid.net/specs/openid-connect-discovery-1_0.html


        MCP Authorization Spec:

        https://modelcontextprotocol.io/specification/draft/basic/authorization


        Returns:

        OpenID Connect Discovery metadata with PKCE support (required by MCP)


        Note:

        This endpoint is functionally equivalent to /oauth-authorization-server

        but uses OpenID Connect Discovery format, which many authorization servers

        (Azure AD, Auth0, etc.) prefer. MCP clients check this endpoint first,

        then fall back to /oauth-authorization-server if not found.


        CRITICAL: code_challenge_methods_supported MUST be present, or MCP clients

        will refuse to proceed (MCP spec requirement).'
      operationId: openid_configuration__well_known_openid_configuration_get
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
  /.well-known/oauth-authorization-server:
    get:
      tags:
      - .well Known
      summary: Oauth Authorization Server
      description: 'OAuth 2.0 Authorization Server Metadata.


        Provides discovery information about the authorization server.


        Spec: RFC 8414 - OAuth 2.0 Authorization Server Metadata

        https://datatracker.ietf.workspace/doc/html/rfc8414


        This server implements its own OAuth2 Authorization Server (Issue #33).

        For MCP clients like Claude Desktop, use API Key authentication instead.


        Returns:

        Authorization server metadata'
      operationId: oauth_authorization_server__well_known_oauth_authorization_server_get
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
  /.well-known/google-connected-apps:
    get:
      tags:
      - .well Known
      summary: Google Connected Apps Verification
      description: 'Domain verification file for Google connected apps (#2773).


        Google''s Connected Console checks that this path answers ``200`` with

        the JSON it issued, with no redirect: ``{"verification_tokens": [...]}``.

        The tokens come from ``GOOGLE_CONNECTED_APPS_VERIFICATION_TOKENS``; they

        are not secret, but they are not logged either. Unset answers ``404``.


        Returns:

        The verification tokens, in the order configured.


        Raises:

        HTTPException: 404 when no token is configured.'
      operationId: google_connected_apps_verification__well_known_google_connected_apps_get
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema:
                additionalProperties:
                  items:
                    type: string
                  type: array
                type: object
                title: Response Google Connected Apps Verification  Well Known Google Connected Apps Get
        '404':
          description: GOOGLE_CONNECTED_APPS_VERIFICATION_TOKENS is not set