Cursor + TrustSEO
Use TrustSEO from Cursor through its remote MCP server support. OAuth keeps your TrustSEO account and Search Console access in the browser-based consent flow.
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 Cursor MCP settings
In Cursor, open Settings and find the MCP or Tools section. You can also configure a remote server in the project MCP configuration when your Cursor version supports it.
Add TrustSEO as a remote server
Add https://trustseo.club/api/mcp as the TrustSEO MCP server URL. Use the remote HTTP/SSE or Streamable HTTP option offered by your Cursor version.
Start OAuth sign-in
Save the server configuration and start it. Cursor should open TrustSEO in your browser when authentication is required.
Approve the connection
Sign in to TrustSEO, choose the account and connected site to authorize, then approve the requested MCP scopes.
Ask a site question
Return to Cursor and ask a question such as “Which pages lost clicks in the last 28 days?” TrustSEO will use only the site access you approved.
How to create a custom connector
If you are building your own MCP connector, use these platform-compatible requirements as a checklist:
- Use the remote server URL https://trustseo.club/api/mcp.
- Allow the client to discover OAuth metadata instead of hard-coding token values.
- Keep PKCE enabled and complete sign-in in the browser opened by Cursor.
- Select only the TrustSEO sites the client needs to access.
Official documentation
Platform features, plan availability, and menu labels can change. Use the official guide for the latest account and workspace requirements.
Open Cursor documentation