TrustSEO

MCP OAuth 2.0 + TrustSEO

A client-agnostic guide to connecting TrustSEO through OAuth 2.0 authorization code flow with PKCE.

TrustSEO MCP server URL

https://trustseo.club/api/mcp

TrustSEO uses OAuth 2.0 with PKCE to connect your account and Google Search Console property. Never paste Google credentials, client secrets, or access tokens into a chat or project file.

Connect TrustSEO step by step

1

Configure the protected resource

Use https://trustseo.club/api/mcp as the MCP server resource. The client should request the protected-resource metadata after an authentication challenge.

2

Discover OAuth endpoints

Use https://trustseo.club/.well-known/oauth-protected-resource/api/mcp, then follow its authorization server to https://trustseo.club/.well-known/oauth-authorization-server.

3

Register the client

If supported, POST the client name and redirect_uris to https://trustseo.club/api/mcp/oauth/register. Public clients should use token_endpoint_auth_method=none.

4

Start authorization with PKCE

Open the authorization endpoint with response_type=code, client_id, redirect_uri, state, resource, and a code_challenge using S256. TrustSEO requires PKCE S256.

5

Approve account and site access

After sign-in, choose the TrustSEO workspace and connected Google Search Console site(s), then approve the requested scopes: sites:read and analysis:read.

6

Exchange and refresh tokens

POST the authorization code and code_verifier to the token endpoint. Store tokens securely, use the access token as a Bearer token, and use refresh_token when the access token expires.

How to create a custom connector

If you are building your own MCP connector, use these platform-compatible requirements as a checklist:

  • Authorization endpoint: https://trustseo.club/api/mcp/oauth/authorize
  • Token endpoint: https://trustseo.club/api/mcp/oauth/token
  • Dynamic registration endpoint: https://trustseo.club/api/mcp/oauth/register
  • Revocation endpoint: https://trustseo.club/api/mcp/oauth/revoke
  • OAuth discovery requires authorization_code, refresh_token, and code_challenge_method=S256.

Official documentation

Platform features, plan availability, and menu labels can change. Use the official guide for the latest account and workspace requirements.

Open MCP OAuth 2.0 documentation