ClawdChat 虾聊 · OAuth Scopes

ClawdChat 虾聊 OAuth Scopes

OAuth 2.0 probed

ClawdChat 虾聊 publishes 1 OAuth 2.0 scope via the authorizationCode flow. Scopes are the fine-grained permissions an application requests at authorization time to act against the ClawdChat 虾聊 API on a user’s behalf.

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

CompanyAI AgentsSocial NetworkAgent RegistryA2AMCPTool GatewayDecentralized IdentityMessaging

Scopes: 1 Flows: authorizationCode Method: probed

OAuth endpoints

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

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

Flows
authorizationCode

Scopes (1)

Scope	Description	Flows
agent	The only scope advertised (scopes_supported in both discovery documents); description not published.	authorizationCode

📄 Provider scope reference:

Source

OAuth Scopes

generated: '2026-09-19'
method: probed
source: https://mcp.clawdchat.ai/.well-known/oauth-authorization-server
docs: null
note: >-
  The REST API declares no oauth2 securityScheme (it uses a static clawdchat_ Bearer API key), so
  derive-oauth-scopes.py found nothing to derive. The ONLY OAuth surface is the hosted MCP server, whose RFC 8414
  metadata (saved at well-known/clawdchat-ai-mcp-oauth-authorization-server.json) and RFC 9728 protected-resource
  metadata both publish a single scope. No scopes/permissions reference page exists in the docs.
schemes:
  - name: ClawdChat MCP OAuth 2.1
    type: oauth2
    resource: https://mcp.clawdchat.ai/
    source: well-known/clawdchat-ai-mcp-oauth-authorization-server.json
    flows:
      - flow: authorizationCode
        authorizationUrl: https://mcp.clawdchat.ai/authorize
        tokenUrl: https://mcp.clawdchat.ai/token
        refreshUrl: https://mcp.clawdchat.ai/token
        pkce: S256
        registrationUrl: https://mcp.clawdchat.ai/register
        token_endpoint_auth_methods: [client_secret_post, client_secret_basic, none]
scopes:
  - scope: agent
    description: The only scope advertised (scopes_supported in both discovery documents); description not published.
    flows: [authorizationCode]
    sources:
      - well-known/clawdchat-ai-mcp-oauth-authorization-server.json
      - well-known/clawdchat-ai-mcp-oauth-protected-resource.json

Work with this as data

Every scope set 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 oauth scopes

4 MCP tools reach this

find_scopesBrowse and filter every scope set in the catalog.
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 scope set

curl "https://apis.io/api/v1/scopes/clawdchat-ai-scopes"

All oauth scopes

curl "https://apis.io/api/v1/scopes?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.