io.github.seer22/shturman-direct-mcp
Related Servers
Alternatives to io.github.seer22/shturman-direct-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceEnables natural language interaction with Yandex Direct API v5 via MCP, providing 113 generated methods with accurate handling of monetary amounts and 64-bit IDs, plus a command-line mode.1342 npm1MIT
- AlicenseNot gradedqualityFmaintenanceMCP server for Yandex Direct, Metrika, Wordstat, and Webmaster APIs, providing 132 tools to manage advertising campaigns, analytics, keyword research, and reporting through any MCP-compatible client.59MIT
- AlicenseCqualityAmaintenanceEnables managing Yandex.Direct contextual advertising campaigns directly from an MCP client chat, covering campaigns, ad groups, ads and moderation, keywords and bids, negative keywords, bid adjustments, retargeting, feeds, statistics, search queries, and account balance. All monetary values are handled in rubles and 64-bit IDs are kept as strings to avoid precision loss.60547 npm1MIT
- AlicenseCqualityDmaintenanceMCP server for the Meta Marketing API with 118 typed tools across ads, insights, pixels/CAPI, pages, Instagram, WhatsApp, catalogs, audiences, leads, and billing, featuring secure token storage and a confirmation gate on destructive calls.1001MIT
- FlicenseNot gradedqualityCmaintenanceEnables management of Google Ads accounts via MCP, providing read and write tools for campaigns, ad groups, keywords, assets, and more, with support for reporting and mutations.-
- AlicenseNot gradedqualityAmaintenanceProvides MCP clients typed tools for Apple Ads Platform research, reporting, auditing, and receipt-gated campaign management with a local-first, read-only-by-default safety model.5MIT
TDQS
Scored across 11 tools
Each tool targets a distinct operation or API: status, Wordstat, Direct read/plan/apply/report, media attach, and separate Metrika and Audience read/write pairs. The two-phase plan/apply design and explicit credential separation make misselection unlikely.
All tools share the direct_ prefix and snake_case, which gives the set a recognizable family resemblance. However, the second part mixes nouns, verbs, and domain suffixes—read/plan/apply versus status/wordstat/metrika_goals—so it is not a strict verb_noun pattern.
11 tools is well within the appropriate range for a server spanning Direct, Wordstat, Metrika, and Audience. Each tool covers a broad surface—direct_read alone handles all reading methods—so none feels redundant or superfluous.
The set provides read, write, report, and media paths across several APIs, and the direct_plan/direct_apply pattern covers arbitrary Direct writes. However, starting ads and unarchiving are explicitly absent, and Audience/Metrika writes are limited to one goal type and one geo-segment path, leaving notable lifecycle gaps.