Skip to main content
HireOtto implements the Model Context Protocol (MCP) as a remote server, exposing a set of tools your AI assistant can call to read and modify your Google Ads account. This page describes the server’s transport options, endpoint URL, and how the protocol works from your perspective as a user.

​
Endpoint

The HireOtto MCP server is available at: 
https://mcp.hireotto.com/sse
This is the URL you add to your AI tool’s MCP configuration. No port specification is needed.

​
Supported transports

stdio transport is not supported. HireOtto is a remote server and requires a network transport (SSE or HTTP).

​
Authentication flow

When your AI assistant first invokes a HireOtto tool, the server checks for a valid Google Ads OAuth token. If none exists, HireOtto returns an authorization URL in its response. Your AI tool will surface this URL to you — click it to complete the Google OAuth consent flow and grant access. After authorization, the token is stored (encrypted) on HireOtto’s servers and associated with your session. Subsequent tool calls use the stored token automatically. See Authentication for a step-by-step walkthrough.

​
How tools are invoked

You don’t call MCP tools directly. Instead, you describe what you want to your AI assistant in plain English, and the assistant decides which tool to call. For example:
What you sayTool invoked
”List my active campaigns”list_campaigns
”Create a Search campaign with $50/day budget”create_campaign
”Show me performance for last month”get_performance_report
”Add ‘running shoes’ as a phrase match keyword”add_keywords
You can also ask your AI to explain which tool it’s using or to confirm before making changes.

​
Tool listing

See MCP Tools for a full list of available tools and their parameters.