VS Code + TrustSEO
Use TrustSEO with VS Code or another MCP-compatible editor that supports remote servers and OAuth 2.0 discovery.
TrustSEO MCP server URL
https://trustseo.club/api/mcpTrustSEO 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
Open MCP server configuration
Open the editor’s MCP server or Copilot tools configuration. In VS Code, use the MCP server configuration command or the workspace MCP configuration file.
Add TrustSEO as a remote server
Set the server URL to https://trustseo.club/api/mcp and choose the remote HTTP transport supported by your editor version.
Start the connection
Run or start the TrustSEO MCP server from the editor. A compatible client will discover that the endpoint requires OAuth 2.0.
Authorize in the browser
Sign in to TrustSEO, choose the account and sites to share, and approve access. Return to the editor after consent completes.
Use TrustSEO tools
Ask for query, page, click, and impression analysis for the connected site from the editor’s chat or agent interface.
How to create a custom connector
If you are building your own MCP connector, use these platform-compatible requirements as a checklist:
- The client must support OAuth 2.0 authorization code flow with PKCE S256.
- Use dynamic client registration when supported; otherwise follow the client’s registered redirect URI setup.
- Preserve the resource parameter as https://trustseo.club/api/mcp.
- Use read-only TrustSEO scopes unless your client specifically needs more access.
Official documentation
Platform features, plan availability, and menu labels can change. Use the official guide for the latest account and workspace requirements.
Open VS Code documentation