Google Ads MCP Server (bjorndavidhansen/google-ads-mcp-server) is an MCP server listed on the M8ven Trust Index. It scores 64 out of 100, grade C. It declares 69 tools. No publisher has claimed this listing.

C
Limited view
64/100

Google Ads MCP Server

Enables Claude Desktop to access and manage Google Ads data, including campaigns, ad groups, keywords, budgets, and visualizations, through natural language interactions.

Limited view. Automated analysis covers part of this stack. Findings reflect what we verified. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

Limited view: static analysis for Python is partially covered.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

bjorndavidhansen

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

Install from

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
🔐
You'll be asked for 4 credentials: POSTGRES_PASSWORD, GOOGLE_ADS_DEVELOPER_TOKEN, GOOGLE_ADS_CLIENT_SECRET, GOOGLE_ADS_REFRESH_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configAPP_ENVSet to dev, test, or prod to specify the environment
configLOG_LEVEL
configUSE_CACHE
configCACHE_TTL
configDB_TYPE
configDB_PATH
configPOSTGRES_HOST
configPOSTGRES_PORT
configPOSTGRES_DATABASE
configPOSTGRES_USER
🔐 secretPOSTGRES_PASSWORD
configPOSTGRES_SSL_MODE
configAPI_HOST
configAPI_PORT
configGOOGLE_ADS_CONFIG_PATH
configGOOGLE_ADS_LOGIN_CUSTOMER_ID
configGOOGLE_ADS_CLIENT_CUSTOMER_ID
configAPP_VERSION
configDB_AUTO_CLEAN_INTERVAL
configPOSTGRES_POOL_MIN_SIZE
configPOSTGRES_POOL_MAX_SIZE
🔐 secretGOOGLE_ADS_DEVELOPER_TOKEN
configGOOGLE_ADS_CLIENT_ID
🔐 secretGOOGLE_ADS_CLIENT_SECRET
🔐 secretGOOGLE_ADS_REFRESH_TOKEN
configCACHE_ENABLED
configENABLE_OTEL
configOTEL_EXPORTER_OTLP_ENDPOINT
configENABLE_METRICS
configENABLE_ACCOUNT_HIERARCHY
configENABLE_DETAILED_REPORTING
configENABLE_CLAUDE_ARTIFACTS
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPORT
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

69/69 tools missing one or more hints — get_ad_groups (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_ad_groups_json (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_ad_group_performance (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +66 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tool inputs are validated

64/69 tool handlers declare input schemas (93%)

Declare an inputSchema with zod/joi/yup on every tool definition.

License file

No license file

Add a LICENSE file (MIT, Apache-2.0, etc.).

Tests exist

No test files found

Add tests that exercise each declared tool.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 5 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/bjorndavidhansen/google-ads-mcp-server)](https://m8ven.ai/mcp/bjorndavidhansen/google-ads-mcp-server)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 396cad681975c12c6446b89eef7c28f8839c6a46
code hash: 179694b13610d97346a9483400929fb66ea61921817d2559c34a2fdce19514ce
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client