mcpgate

mcpgate .well Known API

The .well Known API from mcpgate — 11 operation(s) for .well known.

GitHub OpenAPI

Operations 11

GET /.well-known/oauth-authorization-server Oauth Authorization Server #
GET /.well-known/openid-configuration Openid Configuration #
GET /.well-known/jwks.json Openid Jwks #
GET /.well-known/oauth-authorization-server/sse Oauth Authorization Server Sse #
GET /.well-known/oauth-authorization-server/mcp Oauth Authorization Server Mcp #
GET /.well-known/oauth-protected-resource Oauth Protected Resource #
GET /.well-known/oauth-protected-resource/sse Oauth Protected Resource Sse #
POST /.well-known/client-vault/mcp Client Vault Resolve #
GET /.well-known/oauth-protected-resource/mcp Oauth Protected Resource Mcp #
GET /.well-known/mcp-server-card Mcp Server Card #
GET /.well-known/mcp/server-card.json Mcp Server Card Json Alias #

Specifications

⚙
OpenAPI
https://raw.githubusercontent.com/api-evangelist/mcpgate/refs/heads/main/openapi/mcpgate-well-known-api-openapi.yml

Schemas & Data

📊
JSONSchema
https://raw.githubusercontent.com/api-evangelist/mcpgate/refs/heads/main/json-schema/mcpgate-subscription-row-schema.json
📊
JSONSchema
https://raw.githubusercontent.com/api-evangelist/mcpgate/refs/heads/main/json-schema/mcpgate-issue-request-schema.json
📊
JSONSchema
https://raw.githubusercontent.com/api-evangelist/mcpgate/refs/heads/main/json-schema/mcpgate-customer-update-schema.json
📊
JSONSchema
https://raw.githubusercontent.com/api-evangelist/mcpgate/refs/heads/main/json-schema/mcpgate-message-out-schema.json
📊
JSONSchema
https://raw.githubusercontent.com/api-evangelist/mcpgate/refs/heads/main/json-schema/mcpgate-report-request-schema.json
📊
JSONSchema
https://raw.githubusercontent.com/api-evangelist/mcpgate/refs/heads/main/json-schema/mcpgate-refresh-response-schema.json
📊
JSONSchema
https://raw.githubusercontent.com/api-evangelist/mcpgate/refs/heads/main/json-schema/mcpgate-tool-call-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/mcpgate:mcpgate-well-known-api"
All apis 
curl "https://apis.io/api/v1/apis?limit=25"

Discovery needs no key. Ratings and market analysis are Pro.

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

mcpgate-well-known-api-openapi.yml Raw ↑ 
openapi: 3.2.0
info:
  title: AI Gateway MCP Server .well Known API
  description: Universal MCP Gateway with OAuth integration - Modern Architecture
  version: 2.0.3290
tags:
- name: .well Known
paths:
  /.well-known/oauth-authorization-server:
    get:
      summary: Oauth Authorization Server
      description: OAuth 2.0 Authorization Server Metadata
      operationId: oauth_authorization_server__well_known_oauth_authorization_server_get
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
      tags:
      - .well Known
  /.well-known/openid-configuration:
    get:
      summary: Openid Configuration
      description: 'OpenID Provider Metadata (OpenID Connect Discovery 1.0).


        The scopes the gateway advertises include ``openid``, so a relying

        party such as ChatGPT reads THIS document after the token exchange to

        find the UserInfo endpoint. Without it the party treats the connection

        as failed and starts the authorize flow over.'
      operationId: openid_configuration__well_known_openid_configuration_get
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
      tags:
      - .well Known
  /.well-known/jwks.json:
    get:
      summary: Openid Jwks
      description: The key set behind ``jwks_uri`` — empty, the gateway signs no ID Token.
      operationId: openid_jwks__well_known_jwks_json_get
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
      tags:
      - .well Known
  /.well-known/oauth-authorization-server/sse:
    get:
      summary: Oauth Authorization Server Sse
      description: OAuth 2.0 Authorization Server Metadata for SSE endpoint
      operationId: oauth_authorization_server_sse__well_known_oauth_authorization_server_sse_get
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
      tags:
      - .well Known
  /.well-known/oauth-authorization-server/mcp:
    get:
      summary: Oauth Authorization Server Mcp
      description: OAuth 2.0 Authorization Server Metadata for MCP endpoint
      operationId: oauth_authorization_server_mcp__well_known_oauth_authorization_server_mcp_get
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
      tags:
      - .well Known
  /.well-known/oauth-protected-resource:
    get:
      summary: Oauth Protected Resource
      description: 'OAuth 2.0 Protected Resource Metadata (default: /mcp for ChatGPT Agent compatibility)'
      operationId: oauth_protected_resource__well_known_oauth_protected_resource_get
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
      tags:
      - .well Known
  /.well-known/oauth-protected-resource/sse:
    get:
      summary: Oauth Protected Resource Sse
      description: OAuth 2.0 Protected Resource Metadata for SSE endpoint
      operationId: oauth_protected_resource_sse__well_known_oauth_protected_resource_sse_get
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
      tags:
      - .well Known
  /.well-known/client-vault/mcp:
    post:
      summary: Client Vault Resolve
      description: 'Vault references: a local vault fetches the values behind PII keys.


        Accepts the vault''s own secret only, never an OAuth token. Spec and

        status codes: src/security/client_vault.py.'
      operationId: client_vault_resolve__well_known_client_vault_mcp_post
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
      tags:
      - .well Known
  /.well-known/oauth-protected-resource/mcp:
    get:
      summary: Oauth Protected Resource Mcp
      description: OAuth 2.0 Protected Resource Metadata for MCP endpoint
      operationId: oauth_protected_resource_mcp__well_known_oauth_protected_resource_mcp_get
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
      tags:
      - .well Known
  /.well-known/mcp-server-card:
    get:
      summary: Mcp Server Card
      description: MCP Server Card at the normative SEP-2127 well-known path.
      operationId: mcp_server_card__well_known_mcp_server_card_get
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
      tags:
      - .well Known
  /.well-known/mcp/server-card.json:
    get:
      summary: Mcp Server Card Json Alias
      description: 'Alias for the `.json` form used by earlier (SEP-1649) tooling.


        The SEP-2127 path naming is not yet settled; serving both forms keeps

        discovery working regardless of which path a client probes.'
      operationId: mcp_server_card_json_alias__well_known_mcp_server_card_json_get
      responses:
        '200':
          description: Successful Response
          content:
            application/json:
              schema: {}
      tags:
      - .well Known