Treasury · OAuth Scopes

Treasury OAuth Scopes

OAuth 2.0 searched

Treasury 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 Treasury API on a user’s behalf.

Tokens are issued from https://treasury.app/oauth/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.

CompanyInvestingPersonal FinanceFintechBrokerageFinancial EducationMCPAgent

Scopes: 1 Flows: authorizationCode Method: searched

OAuth endpoints

Authorization URL
https://treasury.app/oauth/authorize

Token URL
https://treasury.app/oauth/token

Flows
authorizationCode

Scopes (1)

Scope	Description	Flows
mcp:connect	Connect to the Treasury Model Context Protocol (MCP) server at https://treasury.app/mcp.	authorizationCode

📄 Provider scope reference:

Source

OAuth Scopes

generated: '2026-07-21'
method: searched
source: https://treasury.app/.well-known/oauth-authorization-server
schemes:
- name: OAuth2
  source: well-known/treasury-oauth-authorization-server.json
  flows:
  - flow: authorizationCode
    authorizationUrl: https://treasury.app/oauth/authorize
    tokenUrl: https://treasury.app/oauth/token
scopes:
- scope: mcp:connect
  description: Connect to the Treasury Model Context Protocol (MCP) server at https://treasury.app/mcp.
  flows: [authorizationCode]
  sources: [well-known/treasury-oauth-authorization-server.json]
notes: >-
  Only one scope (mcp:connect) is advertised in the authorization server
  metadata; it gates access to the MCP server. Individual tool-level scopes, if
  any, are not exposed in the discovery document.