Getgram Authentication

generated: '2026-10-18'
method: searched
generator: extract-docs-artifacts.py (local)
source: https://www.speakeasy.com/docs/ai-control-plane/mcp-gateway/access
sources:
- https://www.speakeasy.com/docs/ai-control-plane/mcp-gateway/access
- https://www.speakeasy.com/docs/ai-control-plane/org-admin/api-keys
- https://www.speakeasy.com/docs/ai-control-plane/guides/oauth-external-server
- https://www.speakeasy.com/docs/standalone-mcp/setting-up-oauth
description: Authentication methods described for Gram (by Speakeasy) MCP servers.
schemes:
- type: http-bearer
  name: Service Account Bearer Token
  evidence: 'Service Account : every caller shares one identity, sent to the upstream service as the Authorization header. The credential is either
    Static (a Bearer token, a Basic username and password, or a Manual header value) or OAuth (an access token the platform obtains for itself
    with the client credentials grant, using a Client Secret or a Signing Client ).'
  location: header
  header: Authorization
  how_to_obtain: Static bearer token configured in the Service Account settings or obtained via OAuth client credentials grant.
- type: http-basic
  name: Service Account Basic Auth
  evidence: 'Service Account : every caller shares one identity, sent to the upstream service as the Authorization header. The credential is either
    Static (a Bearer token, a Basic username and password, or a Manual header value) or OAuth (an access token the platform obtains for itself
    with the client credentials grant, using a Client Secret or a Signing Client ).'
  location: header
  header: Authorization
  how_to_obtain: Static username and password configured in the Service Account settings.
- type: oauth2
  name: Authorization Code Grant
  evidence: The Authorization Code Flow enables user-interactive OAuth with proper consent screens.
  how_to_obtain: User interacts with provider’s authorization endpoint; client receives code and exchanges for token.
- type: oauth2
  name: Client Credentials Grant
  evidence: The Client Credentials grant is a simpler authentication method. The server exchanges a client ID and secret for access tokens.
  how_to_obtain: Server sends client_id and client_secret to token endpoint to obtain access token.
- type: apiKey
  name: API Key
  evidence: API keys authenticate programmatic access to the platform, such as MCP deployments, tool management, telemetry ingestion, and device‑agent
    enrollment.
  location: header
  header: Authorization
  how_to_obtain: Created via Organization settings > API Keys; full token shown once at creation.
docs: https://www.speakeasy.com/docs/ai-control-plane/mcp-gateway/access