Chief · Authentication Profile

Chief Authentication

Authentication

Chief declares 2 security scheme(s) across its OpenAPI definitions.

CompanyAI AgentsAgent ManagementCoding AgentsDeveloper ToolsMCPProject Management

Methods: Schemes: 2 OAuth flows: API key in:

Security Schemes

chief-oauth oauth2

· flows:

relay-device-code device_code

Source

Authentication Profile

generated: '2026-11-03'
method: searched
source: https://chiefisnext.com/docs/mcp
docs: https://chiefisnext.com/docs/mcp
name: Chief authentication
note: Chief publishes no REST/OpenAPI contract. Its only public programmatic surface is the remote MCP server at https://mcp.chiefisnext.com/mcp, protected by OAuth 2.0. Values below come from the docs and from the published discovery documents (GET only); no token, login or registration endpoint was called.
schemes:
- name: chief-oauth
  type: oauth2
  applies_to: https://mcp.chiefisnext.com/mcp
  description: Users connect an assistant (Claude, Codex, Claude Code, ChatGPT, Cursor), sign in to Chief and select which projects the assistant may access on a consent screen.
  flows:
    authorizationCode:
      authorizationUrl: https://chiefisnext.com/oauth/authorize
      tokenUrl: https://chiefisnext.com/oauth/token
      refreshUrl: https://chiefisnext.com/oauth/token
      scopes:
      - projects:read
      - milestones:read
      - summaries:read
      - manager_tasks:read
      - milestones:propose
      - manager_tasks:write
  pkce: S256
  dynamic_client_registration: https://chiefisnext.com/oauth/register
  client_id_metadata_document_supported: true
  revocation_endpoint: https://chiefisnext.com/oauth/revoke
  token_endpoint_auth_methods: [none, client_secret_basic, client_secret_post]
  bearer_methods: [header]
  discovery:
    protected_resource_metadata: https://mcp.chiefisnext.com/.well-known/oauth-protected-resource
    authorization_server_metadata: https://chiefisnext.com/.well-known/oauth-authorization-server
  evidence:
  - url: https://mcp.chiefisnext.com/.well-known/oauth-protected-resource
    http_status: 200
  - url: https://chiefisnext.com/.well-known/oauth-authorization-server
    http_status: 200
  revocation_docs: "Open Settings → Connected apps to inspect or revoke a connection. Revocation takes effect on the assistant's next request."
- name: relay-device-code
  type: device_code
  applies_to: chief-relay (local relay binary)
  description: "Relay auth: Device code flow — no static API keys stored on your machine. The relay opens a browser verification URL; the user compares the code and selects Approve Device."
  source: https://chiefisnext.com/security

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/chiefisnext-com-authentication"

All security posture

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