Google Ads tools for AI agents

The same connector, reached through the settings menu instead of the plugin page.

1. 1

   Open Apps & Connectors

   In ChatGPT, open Settings → Apps & Connectors and create a new custom connector.

2. 2

   Name it Relvo

   NameRelvoCopy
3. 3

   Point it at Relvo

   Connectionhttps://app.relvo.si/mcpCopy
4. 4

   Authenticate

   Choose OAuth, continue, and approve Relvo in the browser. ChatGPT saves the connector to your account.

5. 5

   Ask for the right tool

   PROMPT

   Using Relvo, find the Google ads stripe.com is running right now, with headline, description, landing page and first-seen date. Show me the price before the call, then call it.

   Copy

   The agent picks the matching tools and their prices, then relays the chosen provider's response verbatim.

All 215 catalogued Google Ads endpoints use one token. Those on Relvo's key draw on one prepaid balance, with the price quoted before the call; the rest run on your own provider key or connected Google Ads account.

Use this on a phone, in a locked-down workspace, or whenever you would rather add the connector through Claude's own menu.

1. 1

   Open Connectors

   In Claude, go to Customize → Connectors and choose + Add → Add custom connector.

2. 2

   Name the connector

   NameRelvoCopy
3. 3

   Paste the MCP URL

   Server URLhttps://app.relvo.si/mcpCopy
4. 4

   Sign in

   Click Add, choose Sign in now under Authentication, and approve Relvo in the OAuth window. The Relvo tools appear under the connector.

5. 5

   Ask for the right tool

   PROMPT

   Using Relvo, find the Google ads stripe.com is running right now, with headline, description, landing page and first-seen date. Show me the price before the call, then call it.

   Copy

   The agent picks the matching tools and their prices, then relays the chosen provider's response verbatim.

All 215 catalogued Google Ads endpoints use one token. Those on Relvo's key draw on one prepaid balance, with the price quoted before the call; the rest run on your own provider key or connected Google Ads account.

Project scope lives in a file, so the whole team gets Relvo without running a command.

1. 1

   Add the server

   JSON · .mcp.json

   {
     "mcpServers": {
       "relvo": {
         "type": "http",
         "url": "https://app.relvo.si/mcp"
       }
     }
   }

   Copy

   Create .mcp.json in the project root and add relvo as an HTTP server.

2. 2

   Reload and sign in

   Start a Claude Code session, run /mcp, choose Relvo → Authenticate, then reload. The tools are available in that project.

3. 3

   Ask for the right tool

   PROMPT

   Using Relvo, find the Google ads stripe.com is running right now, with headline, description, landing page and first-seen date. Show me the price before the call, then call it.

   Copy

   The agent picks the matching tools and their prices, then relays the chosen provider's response verbatim.

The same entry works for every project when it is added at user scope instead of project scope. All 215 catalogued Google Ads endpoints use one token. Those on Relvo's key draw on one prepaid balance, with the price quoted before the call; the rest run on your own provider key or connected Google Ads account.

Two settings and one reload — the same entry Hermes would write itself.

1. 1

   Open the config

   Edit ~/.hermes/config.yaml, the file Hermes reads at start-up.

2. 2

   Add the server

   YAML

   mcp_servers:
     Relvo:
       url: https://app.relvo.si/mcp
       auth: oauth

   Copy
3. 3

   Reload and sign in

   In a session, run /reload-mcp, then approve the OAuth prompt Hermes shows. Tokens are cached under ~/.hermes/mcp-tokens/.

4. 4

   Ask for the right tool

   PROMPT

   Using Relvo, find the Google ads stripe.com is running right now, with headline, description, landing page and first-seen date. Show me the price before the call, then call it.

   Copy

   The agent picks the matching tools and their prices, then relays the chosen provider's response verbatim.

All 215 catalogued Google Ads endpoints use one token. Those on Relvo's key draw on one prepaid balance, with the price quoted before the call; the rest run on your own provider key or connected Google Ads account.

Use the global or the project file when you want the entry under your own control.

1. 1

   Open the MCP config

   Edit ~/.cursor/mcp.json for every project, or .cursor/mcp.json inside the repository for one.

2. 2

   Add Relvo

   JSON

   {
     "mcpServers": {
       "relvo": {
         "url": "https://app.relvo.si/mcp"
       }
     }
   }

   Copy
3. 3

   Reload Cursor

   Save the file and reload the window. Relvo appears in the MCP panel, and Authenticate finishes the sign-in.

4. 4

   Ask for the right tool

   PROMPT

   Using Relvo, find the Google ads stripe.com is running right now, with headline, description, landing page and first-seen date. Show me the price before the call, then call it.

   Copy

   The agent picks the matching tools and their prices, then relays the chosen provider's response verbatim.

All 215 catalogued Google Ads endpoints use one token. Those on Relvo's key draw on one prepaid balance, with the price quoted before the call; the rest run on your own provider key or connected Google Ads account.

Grok Bot's settings have no field for a server URL; custom MCP servers are added from the conversation.

1. 1

   Describe the server

   NameRelvoCopy

   Server URLhttps://app.relvo.si/mcpCopy

   Ask the Bot to add a custom server with this name and URL. Say custom server, or it may offer a catalog plugin instead.

2. 2

   Confirm

   The Bot repeats the name and URL. Check that the URL is https://app.relvo.si/mcp, then select Add it.

3. 3

   Authorise

   Select Authorize on the card the Bot sends, sign in and allow access. The Relvo tools appear once you are signed in.

4. 4

   Ask for the right tool

   PROMPT

   Using Relvo, find the Google ads stripe.com is running right now, with headline, description, landing page and first-seen date. Show me the price before the call, then call it.

   Copy

   The agent picks the matching tools and their prices, then relays the chosen provider's response verbatim.

All 215 catalogued Google Ads endpoints use one token. Those on Relvo's key draw on one prepaid balance, with the price quoted before the call; the rest run on your own provider key or connected Google Ads account.