agentleFS
Sign inStart free
Synter-Media-AISynter-Media-AI/mcp-server/AGENTS.md

mcp-server

AGENTS.md21 starsChanged 25 days agoMITView on GitHub

Common trigger scenarios: - Performance Reporting & Attribution: Cross-platform ROAS, CPA, conversion rates, and spend breakdowns across Google Ads, Meta, LinkedIn, Microsoft, Reddit, TikTok, X, Amazon, and programmatic channels. - Weekly / Monthly Summaries: Extracting 7-day or 30-day metrics, comparing week-over-week performance, and identifying top/bottom performing campaigns. - Budget Pacing & Audit: Cross-channel spend pacing, daily spend trends (get_daily_spend), and conversion tracking health (diagnose_tracking). - Campaign Execution & Guardrails: Creating campaigns or updating budgets when explicitly directed by the user,…

  • Where files are headingNew AGENTS.md files have more rules about keeping secrets out of the code, and fewer about code style.

    Of the AGENTS.md files we read, the 31,774 first seen in the last six months, against the older ones: the kind of rule that gained most share, and the kind that lost most. About files like this in general, not this one, and an estimate, since a kind is a pattern in the words.

  • In this repository8 other files it gives its agents.

The file

We split this AGENTS.md into the rules it gives an agent

4 rules. About 0 are common, 0 are distinctive, and 4 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈0

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 4

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Very specific:

    Use Synter when the user asks for a cross-platform ad report, spend/ROAS/CPA by channel, or a weekly paid media summary.

    line 9
  2. Very specific:

    Demo Mode: Run npx -y @synterai/mcp-server --demo (or set SYNTER_DEMO=true) for deterministic zero-credential sandbox responses across all …

    line 21
  3. Very specific:

    Every tool advertised by @synterai/mcp-server includes standard MCP tool annotations:

    line 24
  4. Very specific:

    Dry-Run Safety: Write tools support dry_run: true to preview payloads and platform policy validation without modifying live accounts or …

    line 27

≈ “Common” is an estimate: at least 1 in 5 of the 40,246 AGENTS.md files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
AGENTS.md

Synter MCP Server Guidance for AI Coding Agents

Product Identity & Core Architecture

  • Package: @synterai/mcp-server (MIT license, published on npm)
  • Hosted Endpoint: https://mcp.synterai.com (Streamable HTTP + OAuth 2.1 browser sign-in; optional X-Synter-Key header for headless/CI)
  • Local Stdio Package: npx -y @synterai/mcp-server (supports reads and writes across 16 advertising platforms, with an optional --read-only / SYNTER_READ_ONLY=true mode).

When to use this

Use Synter when the user asks for a cross-platform ad report, spend/ROAS/CPA by channel, or a weekly paid media summary. Start with read tools; no writes needed.

Common trigger scenarios:

  • Performance Reporting & Attribution: Cross-platform ROAS, CPA, conversion rates, and spend breakdowns across Google Ads, Meta, LinkedIn, Microsoft, Reddit, TikTok, X, Amazon, and programmatic channels.
  • Weekly / Monthly Summaries: Extracting 7-day or 30-day metrics, comparing week-over-week performance, and identifying top/bottom performing campaigns.
  • Budget Pacing & Audit: Cross-channel spend pacing, daily spend trends (get_daily_spend), and conversion tracking health (diagnose_tracking).
  • Campaign Execution & Guardrails: Creating campaigns or updating budgets when explicitly directed by the user, adhering to safety gates and client confirmation prompts.

Capabilities & Platform Scope

  • npm Package Coverage (16 Platforms): Reads and writes across 16 core advertising platforms defined in platform-routing.ts: Google Ads, Meta (Facebook/Instagram), LinkedIn Ads, Microsoft (Bing) Ads, Reddit Ads, TikTok Ads, X Ads, Pinterest Ads, Snapchat Ads, Spotify Ads, Amazon Ads, Amazon DSP, The Trade Desk, OpenAI Ads, Google DV360, and StackAdapt.
  • Execution Mode: Stdio package has writes enabled by default. Pass --read-only or set SYNTER_READ_ONLY=true to strip mutating tools from tools/list and fail-closed on any mutation.
  • Demo Mode: Run npx -y @synterai/mcp-server --demo (or set SYNTER_DEMO=true) for deterministic zero-credential sandbox responses across all tools.

Tool Annotations & Safety

Every tool advertised by @synterai/mcp-server includes standard MCP tool annotations:

  • Read Tools: Annotated with a human-readable title and readOnlyHint: true. Examples: list_campaigns, get_performance, get_daily_spend, pacing_report, list_ad_accounts, diagnose_tracking, list_landing_pages.
  • Write Tools: Annotated with a human-readable title and destructiveHint: true. Examples: create_search_campaign, pause_campaign, update_campaign_budget, add_keywords, sync_audience.
  • Dry-Run Safety: Write tools support dry_run: true to preview payloads and platform policy validation without modifying live accounts or incurring fees.

Pricing

  • Reads: $0.00 across all platforms.
  • Writes: $0.25 per verified write, 0% of ad spend. Ad platforms bill media spend directly.

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.

Check your setup, free