mcp-activeview
OfficialRelated Servers
Alternatives to mcp-activeview
No user-submitted related servers found.
Related Servers
- FlicenseAqualityCmaintenanceRead-only MCP server that connects Claude Desktop to the publisher-side Ad Manager API so users can browse networks, saved reports, orders, and line items, and run saved reports to pull their rows into a conversation. No tool mutates data, and per-user OAuth ensures each person inherits only their existing account permissions.5-
- AlicenseNot gradedqualityAmaintenanceRead-only MCP server for the Reddit Ads API v3, enabling AI assistants to analyze ad performance, campaigns, reports, and targeting without modifying anything.MIT
- FlicenseNot gradedqualityCmaintenanceA read-only MCP server for the Google Ads API, exposing reporting tools for account summaries, campaigns, performance, search terms, and conversion actions. Enables natural-language queries to Google Ads data without write access.-
- AlicenseBqualityCmaintenanceRead-only MCP server for Google Ads, enabling querying campaigns, ad groups, ads, insights, and keywords without create/update/delete operations.9MIT
- AlicenseBqualityCmaintenanceA read-only MCP server that provides comprehensive access to the TikTok Business API for retrieving advertising data, including campaigns, ad groups, ads, and performance reports.24MIT
- AlicenseBqualityBmaintenanceRead-only MCP server for Meta Ads that lists and reads ad accounts, campaigns, ad sets, ads, ad images, creatives, and fetches insights at various levels.14MIT
TDQS
Scored across 12 tools
Each tool targets a distinct reporting or redirect management operation. Custom GAM reports, KVP reports, session reports, price rules, and redirect paths are all clearly separated, with no overlapping purposes.
Most tools follow a 'get_<noun>_by_<scope>' pattern (e.g., get_custom_gam_report_by_domain) or 'list_<noun>' (e.g., list_redirect_domains). The pattern is consistent snake_case, though get_price_rules deviates slightly by not including a scope.
With 12 tools covering multiple areas (reports, redirects, pricing rules), the count is well-scoped for a read-only dashboard server. Each tool has a distinct purpose and none seem extraneous.
The tool surface covers the main read operations for GAM reports, redirect paths, and pricing rules. Missing write operations (create/update/delete) are likely intentional given the 'view' nature, but could be considered a minor gap for full lifecycle management.