TESSA Marketing & Technology · OAuth Scopes

TESSA Marketing & Technology OAuth Scopes

OAuth 2.0 searched

TESSA Marketing & Technology 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 TESSA Marketing & Technology API on a user’s behalf.

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

Digital MarketingSEOWeb DevelopmentAccessibilityAI Agent ReadinessProfessional ServicesAgent DirectoryA2AMCPAgent-NativeCompany

Scopes: 1 Flows: authorizationCode Method: searched

OAuth endpoints

Authorization URL
https://tessa.tech/oauth/authorize

Token URL
https://tessa.tech/oauth/token

Flows
authorizationCode

Scopes (1)

Scope	Description	Flows
mcp	Sole scope advertised by both the authorization-server metadata (scopes_supported) and the protected-resource metadata; grants access to the WordPress MCP server. No finer-grained read/write split is published.	authorizationCode

📄 Provider scope reference: https://tessa.tech/.well-known/oauth-authorization-server

Source

OAuth Scopes

generated: '2026-09-19'
method: searched
docs: https://tessa.tech/.well-known/oauth-authorization-server
source: well-known/tessa-tech-oauth-authorization-server.json + well-known/tessa-tech-oauth-protected-resource.json
note: >-
  The OpenAPI declares no oauth2 scheme, so 0-working/derive-oauth-scopes.py produced nothing; this file is built
  from the RFC 8414 / RFC 9728 documents TESSA publishes for its WordPress MCP server. Exactly one scope is
  advertised and no scope reference page exists, so descriptions are as thin as the source. The anonymous MCP
  server on aiagent.tessa.tech has no scopes at all.
schemes:
  - name: wordpress-mcp-oauth
    issuer: https://tessa.tech
    resource: https://tessa.tech/wp-json/mcp/mcp-oauth-server
    source: well-known/tessa-tech-oauth-authorization-server.json
    flows:
      - flow: authorizationCode
        authorizationUrl: https://tessa.tech/oauth/authorize
        tokenUrl: https://tessa.tech/oauth/token
        pkce: S256
        client_auth: none (public clients)
        client_registration: client_id metadata document (client_id_metadata_document_supported true)
scope_count: 1
scopes:
  - scope: mcp
    description: Sole scope advertised by both the authorization-server metadata (scopes_supported) and the protected-resource metadata; grants access to the WordPress MCP server. No finer-grained read/write split is published.
    flows: [authorizationCode]
    sources: [well-known/tessa-tech-oauth-authorization-server.json, well-known/tessa-tech-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/tessa-tech-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.