Read the AdsMCP Free Use Rules and see whether this local installation has accepted the current version.

Accept the current AdsMCP Free Use Rules for this local data directory. Review ads_free_use_rules first.

Show the local Git changes and GitHub fork setup without publishing anything.

Prepare an optional GitHub fork for publishing reviewed AdsMCP changes. confirm=true may create the fork through the configured GitHub token.

Review the changedFiles from ads_github_contribution_status, then create one GitHub branch and pull request after confirm=true.

Create a project that groups related advertising campaigns and their analytics.

Get one local advertising project by its id.

List projects, optionally filtered by active or archived status.

Update project metadata or archive it without deleting its campaigns.

Calculate aggregate and per-campaign KPIs for one project.

Create a local client profile with per-person context. Telegram remains the default channel; channel and external_user_id can represent Mastodon or another connector. contact_account_id records which local connected account made the contact. Consent defaults to unknown; this tool does not send a message.

Get one local client profile and its recent dialogue history.

List local client profiles without loading full dialogue histories.

Update one local client profile, including context, consent status, next action and the local account used for contact. This tool does not send a message.

Append an inbound, outbound or internal note to a local client profile. For external or multi-account contacts, pass contact_account_id so the exact account is recorded. This stores history only and never sends a message.

Send a saved client-profile draft (firstContact or replyToUnread) to up to 50 active profiles with one explicit batch confirmation. The exact saved draft and every variation must have been approved before sending; any draft change requires fresh approval. Requires Telegram Premium, reports a read-only unread-human-dialog preflight without blocking the write, performs an activity preflight (stale exact last-seen and hidden profiles without an avatar are blocked), enforces at least 15 seconds between messages, blocks opted_out profiles, stops on the first send error, and records each successful outbound message.

Take a fast read-only snapshot of unread one-to-one human Telegram chats. This returns the latest incoming message only; it does not read full history, mark messages as read, or send anything. Before drafting a reply when a person may have multiple messages, run the local full-history sync script npm run telegram:sync:unread and review every returned message.

Review the public channel linked in a Telegram user's profile and search it for AI-related topics. Uses the selected local GramJS/TDLib backend, never reads non-public chats, never sends messages, and stores only the bounded review result in the client profile.

Save or update one public discovery candidate in the local interest registry. This does not create a client profile, follow anyone or send a message; consent remains unknown by default.

List public discovery candidates from the local interest registry. This is read-only and never contacts anyone.

Store one bounded public research post linked to an interest contact. This is local research only and never publishes or contacts anyone.

List bounded public research posts collected during discovery. Read-only; it never contacts authors.

List aggregated hashtags and research tags from the local discovery base. Read-only.

Build a local time-window snapshot of research demand: post volume, unique authors, contacts, relevance and popular tags. This is analytics only and never contacts anyone.

List saved research demand snapshots and tag popularity metrics. Read-only analytics; it never contacts anyone.

Save or update one public Telegram group/channel discovered for AI-related topics. This writes only local chat metadata under a project and never collects participants or sends messages.

List public Telegram AI-related chats saved in the local catalog; defaults to the Neron project and never returns participant data.

Save or update one Telegram group or channel in the generic local resource catalog. This stores metadata only and never joins, leaves or sends messages.

List generic Telegram groups and channels saved in the local tg_resources catalog; defaults to the Neron project and never returns participant data.

Record a confirmed Telegram publication link for a cataloged group or channel. This only updates the local audit trail and never sends a message.

List confirmed Telegram publication links recorded for local resources; this is read-only and never sends messages.

Save or update one public Telegram reply/mention found under a message from the connected account. Local-only; never sends or marks messages read.

List public Telegram replies and mentions saved in the local audit table; pending items are shown first and nothing is sent.

Set the review status of one saved public Telegram reply. This changes only local audit data and never sends a message.

Read a bounded recent history in selected public Telegram chats and save direct replies plus a small context window after each outgoing message, because people may answer without using Telegram's reply action. Requires Premium; never sends, joins, collects participant lists or marks messages read.

List public Telegram posts saved from the global AI search. Results are classified locally as request, opportunity, discussion, promotion or repost; this tool never sends messages.

Reclassify saved public Telegram AI posts and rebuild Neron offer matches plus contextual public reply drafts. Local-only: never sends or edits Telegram messages.

Save or update one Telegram AI search phrase for later discovery and demand analysis. This changes only local SQLite and never searches or sends messages.

List saved Telegram AI search phrases and their last-run/result counters; read-only and never contacts Telegram.

List the append-only history of Telegram AI searches, including source/scope, status, quota and result counters; read-only and never contacts Telegram.

Extract normalized demand keywords from one search query or user-provided text and update local trend counters. The submitted text is not stored and this tool never contacts Telegram.

List aggregated Telegram AI demand keywords with source counters and recent-vs-previous trend direction; read-only and never contacts Telegram.

List aggregated demand-topic trends that group related keyword variants, with source counters and recent-vs-previous activity; read-only and never contacts Telegram.

Rebuild demand keyword observations from existing search history, saved public AI posts and inbound client messages. Set reset=true only to replace the derived keyword aggregate and observation tables; stores only normalized keywords and source metadata; never sends messages.

Build one weekly demand snapshot grouped by topic and intent, with deduplicated source counts. This changes only local analytics tables and never contacts Telegram.

List saved weekly demand snapshots by topic and intent; read-only and never contacts Telegram.

Create a local advertising campaign definition, optionally inside a project. It starts in draft status.

Get one campaign by its local id.

List local campaigns, optionally filtered by project and lifecycle status.

Update campaign metadata, lifecycle status or project assignment.

Ingest a funnel event or conversion. A stable dedupe_key makes retries safe.

Record spend and daily platform metrics. A stable dedupe_key makes sync retries safe.

Calculate spend, funnel and efficiency KPIs for one or all campaigns.

Read normalized time-bucketed provider metrics saved in local SQLite.

Attribute local conversion events to tracked touchpoints using a selected attribution model.

Register an external advertising, CRM or webhook integration without storing secrets.

List registered integrations and built-in adapter capabilities/configuration status.

Show adapter readiness, required environment keys and safe next actions for one or all providers.

Explain what audience and acquisition scenario each advertising platform fits before configuring its MCP module.

Show configured provider MCP modules without starting them. Modules keep their own API logic and credentials outside the AdsMCP database.

Start the local AdsMCP settings page on 127.0.0.1. It stores Click.ru data, Yandex Direct OAuth token files and settings, Microsoft Advertising OAuth profiles and Mastodon OAuth account tokens locally, and provides the preferred local Telegram account / GramJS login flow; it never performs billing or campaign actions. Use restart=true only to replace an already-running page.

Stop the local AdsMCP settings page. This does not delete Click.ru profiles, Microsoft OAuth profiles, Mastodon accounts or campaign drafts.

Show locally stored Click.ru advertiser profiles with masked INNs and the active profile. Never returns API tokens.

Show locally stored Click.ru campaign drafts, their statuses and the active campaign. Drafts are not sent or launched.

Change a locally stored Click.ru campaign between DRAFT and READY. This never sends or launches the campaign.

Discover tools exposed by one configured provider MCP module.

Call a tool of a configured provider MCP module, optionally restricted by its allow_tools list. Use provider-native tools for capabilities that AdsMCP does not reimplement.

Read daily Google Ads campaign metrics through the configured service-account adapter. This tool never writes to Google Ads.

Read Google Ads metrics and persist normalized campaign, spend and aggregate conversion data into local SQLite. This never writes to Google Ads.

Replace the enabled landscape and portrait marketing images in one Google Ads Performance Max asset group. New images are linked first; square images, logos and text assets are preserved. Requires explicit confirm=true.

Read aggregate Microsoft Advertising campaign metrics through the official read-only MCP. This tool never writes to Microsoft Ads.

Read aggregate Microsoft Advertising metrics and persist normalized campaigns, spend and conversions into local SQLite. This never writes to Microsoft Ads.

Read Yandex Direct campaign statistics through the configured provider MCP module and normalize the result by day.

Read Yandex Direct statistics through the provider MCP module and persist normalized campaigns, spend and conversions into local SQLite.

Apply an explicitly confirmed, idempotent Yandex Direct campaign change through the provider API. Updates and lifecycle status changes for existing campaigns are exposed; creation uses the dedicated safe create tool and deletion remains disabled.

Create one paused Yandex Direct text campaign through the guarded provider path. The new campaign is created with search and network serving off, without ads or a budget; it cannot start showing until configured and enabled separately.

Read Telegram Ads account, campaigns and normalized metrics through the configured HTTP-based MCP module. This is read-only.

Read Telegram Ads metrics and persist campaigns, daily spend and optional time-bucketed metrics into local SQLite. This never writes to Telegram Ads.

List Telegram Ads cabinets and optionally read one or all cabinets. Switching cabinets requires explicit confirm=true and is restored to the original cabinet afterward.

Read one or all Telegram Ads cabinets and persist their campaigns, daily spend and optional time-bucketed metrics into local SQLite. Cabinet switching requires explicit confirm=true.

Show the official Telegram Ads API layer readiness. With probe=true, perform one read-only getCurrentAccount request; provider writes remain separately guarded.

Create one Telegram Ads advertisement through the official API. This is a provider write; confirm=true is required. Defaults to paused with zero initial budget.

Increase one Telegram Ads ad budget through the official API. This is a provider write; confirm=true is required.

Submit one Telegram Ads ad for moderation through the official API. This is a provider write; confirm=true is required.

Pause or resume one Telegram Ads ad through the official API. This is a provider write; confirm=true is required.

Read Telegram Ads through the official promoteapi.telegram.org API. This is read-only and supports exact date-bounded 5-minute or daily stats.

Read official Telegram Ads API metrics and persist them into the same local SQLite campaign model. This never writes to Telegram Ads.

Check the local Telegram user-account GramJS/TDLib dependencies, credentials, authentication state and ignored storage paths.

Check the official Discord bot connector, credentials and current bot identity. Normal user-account tokens and passwords are not supported.

List Discord servers where the configured bot is installed. This is not a global server search.

List viewable text, announcement, forum and thread channels in one Discord server.

Search members by username or nickname inside one installed Discord server. Finding a member does not authorize contacting them.

Search a bounded recent page of messages in one accessible Discord channel; history is not crawled or persisted.

Send one plain-text message to one selected Discord channel after explicit confirm=true. No bulk sends and no member DMs.

List locally connected Mastodon accounts without returning access tokens.

Start a Mastodon OAuth 2 + PKCE account connection for one instance. Open the returned authorization_url and then complete it with the one-time code.

Complete a pending Mastodon OAuth connection with the one-time code shown by the instance. The code is not logged or returned.

Check the connected Mastodon account and current profile through verify_credentials.

Publish one explicitly provided Mastodon thread in order after confirm=true. Every post after the first replies to the previous post; optionally pin only the thread root.

Pin one selected Mastodon status after explicit confirm=true.

Read a bounded page of Mastodon mention notifications to prepare a context-aware reply. This tool never publishes anything.

Read public Mastodon hashtag timelines for AI-related discovery, score cost/local-model/MCP intent signals and return ranked candidate accounts with bounded post evidence. This never follows or contacts anyone.

Run the expanded Mastodon interest discovery pack for AI agents, MCP, local/self-hosted models, providers, costs and limits; score pain/intent signals and save bounded public evidence to the local research base. This never follows or contacts anyone.

Follow one selected Mastodon account after explicit confirm=true. Search results never trigger follows automatically; read:follows is required to check existing subscriptions and write:follows is required to follow.

Reply to one selected Mastodon status after explicit confirm=true. The target status is checked first, its author mention is added automatically, and the reply visibility cannot be broader than the target.

Send one private Mastodon Direct status to one selected account after explicit confirm=true. The target mention is added automatically; no bulk messaging.

Publish one public Mastodon mention to one selected account after explicit confirm=true. Optionally reply to one public status; no bulk messaging.

Send an explicitly provided ordered list of Mastodon direct messages, public mentions or replies after confirm=true. Each item names its recipient, exact text and mode; discovery never creates items automatically.

Update selected Mastodon profile fields after explicit confirm=true. Unspecified fields remain unchanged.

Continue local Telegram user-account login through the selected backend. GramJS supports starting a local QR flow; never paste Telegram codes or 2FA passwords into a hosted chat.

Read recent history or search one Telegram chat through the connected local GramJS/TDLib account. Requires Telegram Premium; no messages are sent.

Mark one human one-to-one Telegram chat as read. Requires explicit confirm=true; sends no message, does not create a local dialogue row, and does not mark bots or channels.

Search public Telegram channel posts globally by full-text query. Requires Telegram Premium. Uses a free daily quota when available and never spends Stars without explicit confirm_paid=true plus a sufficient max_stars limit.

Create an ordered local Telegram action queue from explicitly supplied targets and exact texts. Requires confirm=true; it does not execute anything. Supports one-to-one messages, group replies, channel-post replies and one-message reactions. No recipient discovery is performed. Each action is assigned a random pause between min_delay_seconds and max_delay_seconds (default 15–66 s) before it runs.

List the exact actions and statuses in one local Telegram action queue. Read-only; it does not send or mark anything read.

Execute an explicitly approved Telegram action queue in sequence. Requires Premium and confirm=true; verifies each action through the existing send/reply/reaction tools, waits at least the configured interval, and stops on the first error without retrying.

Cancel all still-queued actions in one local Telegram action queue. Requires confirm=true; already sent or failed actions are not changed.

Send one plain-text Telegram message through the selected local GramJS/TDLib account. Requires Telegram Premium, prior approval of the exact text, and explicit confirm=true; reports a read-only unread-human-dialog preflight without blocking the write; bulk outreach is not supported.

Add one emoji reaction to one existing Telegram message through the selected local GramJS/TDLib account. Requires Telegram Premium, explicit confirm=true and (when available) expected_text to fail closed if the message changed; does not send text or mark the chat read.

Read-only preflight for a broadcast Telegram channel: checks Direct Messages, the connected discussion chat, and public contacts from the channel description. Requires Telegram Premium; never joins, sends a message, or creates a public post.

Send one explicitly approved plain-text message to a Telegram channel's Direct Messages monoforum, only when a read-only preflight confirms that Direct Messages are enabled. Requires Telegram Premium and confirm=true; never publishes to the channel feed.

Reply publicly to one Telegram channel post through its linked discussion only when the post contains a relevant explicit request and the resource rules permit it. Requires Telegram Premium and explicit confirm=true; reports a read-only unread-human-dialog preflight without blocking the write; never sends a private message and never bypasses moderation or guest-send restrictions.

Reply publicly to one message inside an accessible Telegram group when the message contains a relevant explicit request and the resource rules permit it. Requires Telegram Premium and explicit confirm=true; reports a read-only unread-human-dialog preflight without blocking the write; never sends a private message and never bypasses moderation, CAPTCHA or guest-send restrictions.

Create a KPI rule. Supported actions are pause_campaign and notify.

List automation rules, optionally for one campaign.

Evaluate automation rules. This is dry-run unless execute=true is explicitly set.

Show local SQLite storage path, row counts and safety defaults.

Check the optional Ads Network Relay connection. The local MCP works without it.

Show the dStore card and advertising-placement adapter configuration. It reads public catalog data and does not send credentials or publish changes.

Search dStore's verified public advertising inventory. Use this for requests to find channels or sites for mutual promotion; AIKI community proposals are separate and remain unverified until dStore checks them.

Read one public dStore card by numeric id or dStore card URL. Returns normalized title, resource URL, icon, platform, tags and description for catalog discovery.

Read up to 50 public dStore cards by id or URL. The result keeps successful cards and reports individual lookup errors.

Show the AIKI community source for AdsMCP. AIKI proposals are unverified leads; dStore must verify them before adding a platform to the catalog.

Return the AIKI MCP configuration plus the AdsMCP workflow: search the community topic, check duplicates and topic rules before publishing a new channel or advertising offer, then hand the unverified proposal to dStore.

List verified or reported advertising platforms from the optional network registry.

Anonymously report a new advertising platform or integration candidate. No credentials are sent.

Publish an opt-in networking profile without advertising credentials or raw campaign data.

Find opt-in networking profiles in the optional relay registry.

Publish an opt-in advertising placement offer. Provider credentials stay local.

List verified advertising placement offers from the optional relay registry.

Opt-in anonymous conversion report. Send only opaque references and aggregates, never raw PII or credentials.

Opt-in publish of aggregated campaign metrics. The relay never receives raw local events.

Pull opt-in network catalog changes since an ISO timestamp.