Hi Antigravity team,
I would like to request Sitelemetry for the Antigravity MCP Store. Sitelemetry gives agents evidence-backed website audits across security, technical SEO, AI visibility, analytics integrations, accessibility, and performance, with prioritized remediation guidance.
Remote MCP endpoint: https//sitelemetry.com/mcp
Authentication: browser-based OAuth with PKCE and dynamic client registration; no API key to paste. An unauthenticated MCP request returns the expected 401 challenge and OAuth discovery metadata.
Setup guide: sitelemetry. com/mcp-guide
Website: https//sitelemetry.com
A custom Antigravity configuration can use mcpServers.sitelemetry.serverUrl = “https//sitelemetry.com/mcp”. We have not claimed an Antigravity Store listing or Antigravity-specific certification. Could you share the official listing process or consider adding Sitelemetry to the Store? I can provide any additional details or test access needed.
Thank you,
Ozan Dikici
Sitelemetry
Hey @Ozan_Dikici , welcome!
Tagging your post with [MCP Store] kicks off the official review, but you can also actually use Sitelemetry as a custom remote server right now.
Here is how to get it running today:
-
Update your config file Add this snippet to your ~/.gemini/config/mcp_config.json (or your workspace’s .agents/mcp_config.json):
-
{
"mcpServers": {
"sitelemetry": {
"serverUrl": "https://sitelemetry.com/mcp"
}
}
}
(Double-check that you didn’t miss the colon in https://!)
-
Authenticate with OAuth Go to Settings (Cmd+, or Ctrl+,) → Customizations → Installed MCP Servers. Find sitelemetry and click Authenticate. Antigravity will handle the DCR flow automatically.
Let us know if you run into any snags!
Thanks @Ambati_Rajendra — you are right, the colon was missing. The original post is locked for editing, so here are the corrected details for the MCP Store reviewers:
- Remote MCP endpoint:
sitelemetry
-
-
- Website:
sitelemetry
Custom Antigravity config:
{ "mcpServers": { "sitelemetry": { "serverUrl": "sitelemetry" } } }
Authentication is browser OAuth (PKCE + dynamic client registration); an unauthenticated request returns the expected 401 challenge with OAuth discovery metadata. Happy to provide test access or anything else the Store review needs.