Contra · OAuth Scopes

Contra OAuth Scopes

OAuth 2.0 searched

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

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

CompanyFuture Of WorkFreelance MarketplaceTalentHiringProfessional NetworkModel Context ProtocolDeveloper API
Scopes: 1 Flows: authorizationCode Method: searched

OAuth endpoints

Authorization URL
https://contra.com/api/mcp/oauth/authorize
Token URL
https://contra.com/api/mcp/oauth/token
Flows
authorizationCode

Scopes (1)

ScopeDescriptionFlows
mcp:tools Grants an authorized client access to invoke the tools exposed by the Contra MCP server (https://contra.com/mcp). authorizationCode

Source

OAuth Scopes

Raw ↑
generated: '2026-07-18'
method: searched
source: https://contra.com/.well-known/openid-configuration
docs: https://contra.com/.well-known/oauth-protected-resource/mcp
schemes:
- name: McpOAuth2
  source: well-known/contra-openid-configuration.json
  flows:
  - flow: authorizationCode
    authorizationUrl: https://contra.com/api/mcp/oauth/authorize
    tokenUrl: https://contra.com/api/mcp/oauth/token
scopes:
- scope: mcp:tools
  description: >-
    Grants an authorized client access to invoke the tools exposed by the
    Contra MCP server (https://contra.com/mcp).
  flows:
  - authorizationCode
  sources:
  - well-known/contra-openid-configuration.json
notes: >-
  The Contra Public REST API uses a static X-API-Key header (no OAuth
  scopes). OAuth scopes here apply only to the hosted MCP server, which
  advertises a single scope, mcp:tools.