
Advertising · https://googleads.googleapis.com
set up olywork — https://olywork.com/llms.txt
claude mcp add --transport http olywork https://olywork.com/mcp
Settings → Connectors → add https://olywork.com/mcp as a custom connector.
Add https://olywork.com/mcp as a remote MCP connector in its tool settings.
Settings → Connectors → Add custom connector → https://olywork.com/mcp.
Point it at https://olywork.com/mcp (HTTP transport).
curl -fsSL https://olywork.com/install.sh | sh
LangChain, CrewAI or any code: /call/<tool-id> + X-Olywork-Token: <token>. No SDK.
Using olywork, track recent account changes. Show me the price first.
olywork call google-ads.query --method POST --query customer_id=2277522568 --data '{"query":"SELECT customer.id, customer.descriptive_name, customer.currency_code, customer.time_zone FROM customer LIMIT 1"}'Connect once; olywork.com keeps the credential server-side and injects it per call. No key on any machine.
The provider's own rate, $0.000 markup. How billing works.
Calls through your own connection are not metered by olywork.
Connect your account with the provider's supported authentication method.
Another provider is a different word in the prompt, not a new integration.
The same token calls AnyAPI, DataForSEO, Semrush and 3,232 other tools.
google-ads.accountsgoogle-ads.budget.updategoogle-ads.querygoogle-ads.x.gaql-account-budgetgoogle-ads.x.gaql-ad-groupgoogle-ads.x.gaql-ad-group-adgoogle-ads.x.gaql-ad-group-ad-asset-viewgoogle-ads.x.gaql-ad-group-audience-viewgoogle-ads.x.gaql-ad-group-criteriongoogle-ads.x.gaql-ad-schedule-viewgoogle-ads.x.gaql-age-range-viewgoogle-ads.x.gaql-assetgoogle-ads.x.gaql-asset-groupgoogle-ads.x.gaql-audiencegoogle-ads.x.gaql-bidding-strategygoogle-ads.x.gaql-billing-setupgoogle-ads.x.gaql-campaigngoogle-ads.x.gaql-campaign-assetgoogle-ads.x.gaql-campaign-audience-viewgoogle-ads.x.gaql-campaign-budgetgoogle-ads.x.gaql-campaign-criteriongoogle-ads.x.gaql-change-eventgoogle-ads.x.gaql-change-statusgoogle-ads.x.gaql-click-viewgoogle-ads.x.gaql-conversion-actiongoogle-ads.x.gaql-customergoogle-ads.x.gaql-customer-assetgoogle-ads.x.gaql-customer-clientgoogle-ads.x.gaql-detail-placement-viewgoogle-ads.x.gaql-gender-viewgoogle-ads.x.gaql-geographic-viewgoogle-ads.x.gaql-income-range-viewgoogle-ads.x.gaql-keyword-viewgoogle-ads.x.gaql-landing-page-viewgoogle-ads.x.gaql-location-viewgoogle-ads.x.gaql-managed-placement-viewgoogle-ads.x.gaql-paid-organic-search-term-viewgoogle-ads.x.gaql-parental-status-viewgoogle-ads.x.gaql-recommendationgoogle-ads.x.gaql-search-term-viewgoogle-ads.x.gaql-shopping-performance-viewgoogle-ads.x.gaql-topic-viewgoogle-ads.x.gaql-user-interestgoogle-ads.x.gaql-user-listgoogle-ads.x.gaql-user-location-viewgoogle-ads.google.keywords.ideasgoogle-ads.google.keywords.volumeReliability badges come from live traffic through olywork.com. Live-verified means a successful provider check; it does not verify every request variant.
Every provider that does this job, side by side: price per billing unit, measured success rate and speed.
Every provider that does this job, side by side: price per billing unit, measured success rate and speed.
Yes. This is an own-account connection: you sign in to Google Ads once and your agent uses that connection through your olywork.com token. Calls on it are never metered.
Run: claude mcp add --transport http olywork https://olywork.com/mcp. One MCP server carries Google Ads and the rest of the catalog.
Anything that speaks MCP (Claude Code, Claude Desktop, ChatGPT, Codex, Cursor, Grok) and anything that can make an HTTP request (LangChain, CrewAI, LlamaIndex, plain code).
No. olywork.com serves Google Ads's real API through its own metered proxy: the request is the provider's own, the credential is injected server-side, and the answer is relayed verbatim. The official Google Ads channels are linked above.