Skip to content
mcp/harbor

Gemini CLI synter ads builtwith_get_technology_changes

How to: Gemini CLI synter ads builtwith_get_technology_changes

client:Gemini CLI transport:streamable-http tool:builtwith_get_technology_changes

Add synter ads to Gemini CLI

  1. 01

    Open ~/.gemini/settings.json and merge this in. Keep any servers already there. 

{
  "mcpServers": {
    "synter-ads": {
      "httpUrl": "https://mcp.syntermedia.ai/mcp/"
    }
  }
}
  1. 02

    Save the file and restart Gemini CLI.

  2. 03

    Ask for something builtwith_get_technology_changes does. Gemini CLI lists the server's tools on connect and calls builtwith_get_technology_changes itself — you do not invoke it by name.

  3. 04

    If nothing happens, check the server is running and that synter ads's identifier in your config matches the one above exactly.

Gemini expands $VAR and ${VAR} inside env values, so a secret can live in your shell rather than this file. Gemini CLI docs

Set these first

synter ads will not start until these are set, so builtwith_get_technology_changes never becomes available.

  • SYNTER_API_KEY

Same tool, other clients

This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what the server actually exposes, not what its listing claims.

Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.

synter ads MCP server