Skip to main content

​
What you need

HireOtto is a hosted remote MCP service. You do not need a Google Cloud project, LinkedIn developer app, API keys, JSON credentials, a terminal, or a local process.
  • An AI client or agent that supports remote MCP servers over HTTP and OAuth.
  • A HireOtto trial or paid plan.
  • A Google login with access to the Google Ads accounts, Tag Manager containers, Search Console properties, or GA4 properties you want to use – and a LinkedIn identity with access to the required LinkedIn Ads accounts when connecting that server.
Add only the servers you need. Each server is a separate MCP connection, while Search Console is currently available through the Google Ads connection.

​
Choose the HireOtto server URLs

Use this connection for Google Ads reporting and supported account actions. It also exposes Search Console tools, but Search Console requires its own Google authorization after the server is connected.
  • Google Ads: read reporting data and run supported campaign-management actions.
  • Search Console: inspect properties, organic performance, URLs, and sitemaps using a separate Google permission.

​
Google Tag Manager

Use this connection to inspect Tag Manager accounts, containers, workspaces, tags, triggers, variables, folders, and tag wiring.
The current Tag Manager server is read-only. It does not create, edit, delete, or publish container changes.

​
Google Analytics 4 – beta

Use this connection for GA4 property discovery, metadata, report compatibility checks, standard reports, comparisons, and basic realtime reporting.
GA4 access is read-only and currently in beta. HireOtto cannot edit GA4 properties or configuration.

​
LinkedIn Ads – beta

Use this connection to inspect LinkedIn Ads accounts and hierarchy, run performance and professional-demographic reports, resolve targeting entities, estimate audience size, work with supported images, and prepare supported campaign objects as drafts.
LinkedIn Ads is available where access is enabled. Read and write capability depends on the connected ad-account role and, for some sponsored-content workflows, LinkedIn Page permissions.
LinkedIn Ads quickstart

​
Connect HireOtto to your AI client

The menu names below reflect the current client interfaces. Admin controls and feature availability can vary by plan or workspace.

​
Claude

  1. Open Customize → Connectors.
  2. Select +, then Add custom connector.
  3. Give the connection a clear name, such as HireOtto — Google Ads, and paste the matching server URL.
  4. Select Add, then Connect, and complete the authorization prompt.
Claude Free accounts currently support one custom connector. Pro and Max users can add custom connectors directly; Team and Enterprise workspaces have owner-managed setup.

​
ChatGPT

  1. Open Plugins → ’+’ and provide the HireOtto server endpoint.
  2. Give the connection a clear name, such as HireOtto – Google Ads, and paste the matching server URL.
  3. Select Add, then Sign in, and complete the authorization prompt.

​
Make AI Agents

  1. Open the scenario containing Make AI Agents (New) → Run an agent.
  2. From the agent module, select Add MCP.
  3. Create a connection with the matching HireOtto server URL.
  4. Select only the tools the agent needs, then save the connection and the agent.
  5. Test the agent in Make before using it in a live scenario.
Limiting enabled MCP tools keeps the agent’s tool list clearer and can reduce unnecessary model usage.

​
Grok, Perplexity, or another remote MCP client

  1. Open the client’s MCP or tools settings.
  2. Create a remote HTTP MCP connection and paste the matching HireOtto server URL.
  3. Use OAuth if the client asks for an authentication method.
  4. Complete the authorization prompt, enable the server, and confirm that its tools are visible.
HireOtto is hosted remotely, so do not configure it as a local command or stdio process.

​
Complete the platform connection

Connecting the MCP server and connecting the marketing platform are two separate steps. First your AI client connects to HireOtto. Then a HireOtto authentication tool connects the specific Google or LinkedIn service and saves the access granted by that identity.
  1. Ask: “Connect my Google Ads account.”
  2. Open the authorization link returned by HireOtto.
  3. Choose a Google login with access to the required Google Ads account or MCC, grant permission, and select the accounts HireOtto should save.
  4. Return to the AI client and ask: “List my accessible Google Ads accounts.”

​
Google Search Console

  1. In the Google Ads HireOtto connection, ask: “Connect my Google Search Console account.”
  2. Open the authorization link and choose a Google login that can access the required Search Console properties.
  3. Grant the Search Console permission, then ask: “List the Search Console properties I can access.”
Connecting Google Ads does not automatically grant Search Console access. Google treats them as separate services and permissions.

​
Google Tag Manager

  1. Ask: “Connect my Google Tag Manager account.”
  2. Open the authorization link and choose a Google login with access to the required Tag Manager accounts and containers.
  3. Grant read-only Tag Manager access, then ask: “List my Tag Manager accounts and containers.”

​
Google Analytics 4

  1. Ask: “Connect my Google Analytics account.”
  2. Open the authorization link and choose a Google login with access to the required GA4 properties.
  3. Grant read-only Analytics access, then ask: “List my GA4 accounts and properties.”

​
LinkedIn Ads

  • Ask: “Connect my LinkedIn Ads account.”
  • Open the authorization link and sign in with the LinkedIn identity that can access the required ad account.
  • Grant the requested permissions, then ask: “List the LinkedIn Ads accounts I can access, including my role and write capability.”
Viewer access supports read-only work. Creating or changing ads requires a sufficient ad-account role, and some sponsored-content workflows also require access to the associated LinkedIn Page.

​
Verify the connection

Use a small read request before starting a longer workflow. A successful response confirms both the MCP connection and the platform authorization.
  • Google Ads: “List my accessible accounts.”
  • Search Console: “Show the Search Console properties I can access.”
  • Tag Manager: “List my Tag Manager accounts and web containers.”
  • GA4: “List my GA4 accounts and properties.”
  • LinkedIn Ads: “List the LinkedIn Ads accounts I can access, including my role and write capability.”
For Google Ads, ask for an account-specific read next, such as “List the enabled campaigns in account 1234567890.” Review the returned account name and ID before requesting any change.

​
Plans, profiles, and access

  • The free trial, Starter, Pro, and Agency plans include supported core access across Google Ads, Tag Manager, Search Console, GA4 and LinkedIn Ads beta.
  • The trial ends after 14 days or 200 credits, whichever comes first.
  • Starter includes 2,000 credits per month; Pro includes 5,000 credits per month; Agency includes unlimited credits.
  • Agency is required for audits, multiple connected Google profiles, team billing, and additional seats.
  • Connecting another profile means authorizing a different Google login. Giving the same login another nickname does not expand its account access.
HireOtto can access only the accounts, containers, and properties available to the Google login or LinkedIn identity you authorize. It does not bypass platform roles or permissions.

​
Common setup problems

​
The server is connected, but no tools appear

  • Confirm that the endpoint ends with /mcp and matches the intended HireOtto server.
  • Complete the client-level OAuth prompt, then rescan or refresh the server tools.
  • Enable the connector or app in the current chat or agent.
  • Restart or reconnect the client if its MCP tool list is cached.

​
The tool asks you to authenticate again

  • Run the relevant connect prompt and open the newest authorization link.
  • Finish the Google or LinkedIn consent flow in the same browser session and return to the original AI client.
  • If the connection was revoked or the Google password or security policy changed, reconnect the service.

​
No accounts, containers, or properties appear

  • Confirm that the connected Google or LinkedIn login can open the required resource directly in Google’s interface.
  • For Google Ads, refresh accessible accounts after Google grants or changes access.
  • For nested Google Ads manager structures, connect a Google login with direct access to the relevant inner MCC when the account is not discoverable from the existing profile.
  • On Agency, use a distinct profile name when connecting another Google login.
  • For LinkedIn Ads, confirm that the same LinkedIn identity can open the ad account in Campaign Manager and inspect the returned role and write capability.

​
A client menu does not match this guide

MCP client interfaces change frequently. Look for Apps, Connectors, Tools, Integrations, or MCP settings, then add a remote HTTP server with OAuth. If the client does not support remote MCP or OAuth, it cannot complete the hosted HireOtto connection.

​
Security and control

  • HireOtto uses OAuth; you do not paste Google or LinkedIn passwords, API keys, or refresh tokens into the conversation.
  • Google Ads supports both read workflows and supported account actions. Review important or bulk changes before they are applied.
  • Tag Manager and GA4 are read-only in their current releases.
  • Search Console uses its own Google permission and is limited to the resources available to that Google login.
  • LinkedIn Ads supports read workflows and selected draft-first actions where access is enabled. Write capability depends on the connected ad-account role and LinkedIn Page permissions.
  • Disconnect the app in your AI client or revoke the relevant Google or LinkedIn authorization when access is no longer needed.

​
Next steps

After the verification request succeeds, continue with the guide or tools reference for the server you connected. Start with a read workflow, confirm the account or property, and move to reviewable actions only when the server supports them. If setup fails, go to Troubleshooting.