Wato · Authentication Profile

Wato Authentication

Authentication

Wato secures its APIs with oauth2 across 1 declared security scheme, as derived from its OpenAPI definitions. OAuth 2.0 is offered via the authorizationCode and deviceCode flow(s).

CompanyMCPAI AgentsAgent GovernanceTeam MemoryConnectorsAgent SkillsAutomationDeveloper ToolsY Combinator

Methods: oauth2 Schemes: 1 OAuth flows: authorizationCode, deviceCode API key in:

Security Schemes

watoOAuth oauth2

· flows: authorizationCode, deviceCode

Source

Authentication Profile

generated: '2026-07-21'
method: searched
source: https://mesh.watolabs.com/.well-known/oauth-authorization-server
docs: https://docs.watolabs.com/docs/connect-clients
summary:
  types:
  - oauth2
  oauth2_flows:
  - authorizationCode
  - deviceCode
  bearer_methods:
  - header
  notes: >-
    The Wato MCP gateway (https://mesh.watolabs.com/api/mcp) is an OAuth 2.0
    protected resource (RFC 9728 metadata published at
    /.well-known/oauth-protected-resource). Authorization is delegated to a
    WorkOS AuthKit authorization server (RFC 8414 metadata published), with
    PKCE (S256), dynamic client registration, refresh tokens, and the device
    authorization grant. MCP clients (Claude Code, Codex, Cursor) trigger the
    OAuth flow interactively on connect; login, SSO, and directory sync are
    handled by WorkOS. Agents never receive raw connector credentials — the
    gateway executes approved connector tools server-side.
schemes:
- name: watoOAuth
  type: oauth2
  issuer: https://qualified-tree-19-staging.authkit.app
  flows:
  - flow: authorizationCode
    authorizationUrl: https://qualified-tree-19-staging.authkit.app/oauth2/authorize
    tokenUrl: https://qualified-tree-19-staging.authkit.app/oauth2/token
    pkce_methods:
    - S256
  - flow: deviceCode
    deviceAuthorizationUrl: https://qualified-tree-19-staging.authkit.app/oauth2/device_authorization
    tokenUrl: https://qualified-tree-19-staging.authkit.app/oauth2/token
  grant_types_supported:
  - authorization_code
  - refresh_token
  - urn:ietf:params:oauth:grant-type:device_code
  token_endpoint_auth_methods_supported:
  - none
  - client_secret_post
  - client_secret_basic
  registration_endpoint: https://qualified-tree-19-staging.authkit.app/oauth2/register
  introspection_endpoint: https://qualified-tree-19-staging.authkit.app/oauth2/introspection
  jwks_uri: https://qualified-tree-19-staging.authkit.app/oauth2/jwks
  sources:
  - well-known/wato-oauth-authorization-server.json
  - well-known/wato-oauth-protected-resource.json

Work with this as data

Every security artifact 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 security posture

4 MCP tools reach this

find_securityBrowse and filter every security artifact 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 security artifact

curl "https://apis.io/api/v1/security/wato-authentication"

All security posture

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