Server facts
mcp-server
Project
- Author
- Synter-Media-AI
- Repository
- github.com/Synter-Media-AI/mcp-server
- License
- Not specified
- Category
- Finance & Commerce
Tech
- Runtime / language
- Not specified
- Transports
- stdio
- Remote available
- No
- Authentication
- Not specified
Activity
- GitHub stars
- 20
- Last commit
- Data as of
Tags
- advertising
- ai agents
- campaigns
- google ads
- marketing
- mcp
- meta
- tiktok
Overview
Advertising workflows in Synter span account discovery, campaign setup, creative production, and performance review through an MCP connection. Agents can inspect connected accounts and campaigns, retrieve spending and conversion metrics, change daily budgets, and pause campaigns. Google Ads tools cover Search, Display, and Performance Max creation, alongside keyword additions and search exclusions. Separate tools create campaigns for Meta, LinkedIn, and Reddit. Creative tasks include generating images or videos and uploading image assets for ads.
Audience operations support uploads using hashed contact identifiers, mobile identifiers, company domains, CSV sources, or references to staged artifacts. A staging tool places identifier payloads in Synter’s private artifact store for subsequent audience synchronization. Google Ads audience management also covers creating lists, appending members, checking upload jobs, and inspecting linked data sources. For measurement, agents can create or list conversion actions and inspect a website’s tracking installations. Workspace landing pages can be listed with publication status and domain details, while a general tool runner exposes additional Synter operations by name.
mcp-server setup notes
- mcp-server records stdio only; confirm a network transport upstream before planning remote access.
- mcp-server has no recorded license; confirm reuse terms in its repository.