SEO · https://searchconsole.googleapis.com
set up treg — https://treg.tracea.online/llms.txt
claude mcp add --transport http treg https://treg.tracea.online/mcp
Settings → Connectors → add https://treg.tracea.online/mcp as a custom connector.
Add https://treg.tracea.online/mcp as a remote MCP connector in its tool settings.
Settings → Connectors → Add custom connector → https://treg.tracea.online/mcp.
Point it at https://treg.tracea.online/mcp (HTTP transport).
curl -fsSL https://treg.tracea.online/install.sh | sh
LangChain, CrewAI or any code: /call/<tool-id> + X-Treg-Token: <token>. No SDK.
Using treg, clicks, impressions, CTR & top queries. Show me the price first.
treg call google-search-console.x.searchconsole-urltestingtools-mobilefriendlytest-run --method POST
Connect once; treg.to keeps the credential server-side and injects it per call. No key on any machine.
The provider's own rate, $0.000 markup. How billing works.
Calls through your own connection are not metered by treg.
Connect your account with the provider's supported authentication method.
Another provider is a different word in the prompt, not a new integration.
The same token calls every provider in the catalog and 3,274 other tools.
google-search-console.performancegoogle-search-console.sitemapsgoogle-search-console.sitesgoogle-search-console.url_inspectiongoogle-search-console.x.searchconsole-urltestingtools-mobilefriendlytest-rungoogle-search-console.x.webmasters-sitemaps-deletegoogle-search-console.x.webmasters-sitemaps-getgoogle-search-console.x.webmasters-sitemaps-submitgoogle-search-console.x.webmasters-sites-addgoogle-search-console.x.webmasters-sites-deletegoogle-search-console.x.webmasters-sites-getReliability badges come from live traffic through treg.to. Live-verified means a successful provider check; it does not verify every request variant.
Every provider that does this job, side by side: price per billing unit, measured success rate and speed.
Every provider that does this job, side by side: price per billing unit, measured success rate and speed.
Yes. This is an own-account connection: you sign in to Google Search Console once and your agent uses that connection through your treg.to token. Calls on it are never metered.
Run: claude mcp add --transport http treg https://treg.tracea.online/mcp. One MCP server carries Google Search Console and the rest of the catalog.
Anything that speaks MCP (Claude Code, Claude Desktop, ChatGPT, Codex, Cursor, Grok) and anything that can make an HTTP request (LangChain, CrewAI, LlamaIndex, plain code).
No. treg.to serves Google Search Console's real API through its own metered proxy: the request is the provider's own, the credential is injected server-side, and the answer is relayed verbatim. The official Google Search Console channels are linked above.