TrueClicks

com.trueclicksPublished by trueclicks.comOfficial publisherv1.0.1Updated Oct 24, 2026

Audit and monitor PPC accounts: Google Ads, Microsoft Advertising, and Meta Ads.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Remote MCP server that lets an assistant audit and monitor PPC advertising accounts on Google Ads, Microsoft Advertising and Meta Ads.

What you can do
  • Audit and monitor paid search and social ad accounts across Google Ads, Microsoft Advertising and Meta Ads.
  • Review account performance and issues surfaced by TrueClicks' auditing for those platforms.
  • No individual tools are documented in the supplied listing, so exact actions depend on the connected account and the server's own tool set.
When to use it
Useful when you manage or review PPC campaigns and want an assistant to pull TrueClicks audit findings and monitoring information for Google, Microsoft and Meta ad accounts into a conversation.
Requirements
A remote MCP endpoint at data.trueclicks.com over streamable HTTP, with OAuth sign-in required. A TrueClicks account with access to the ad accounts you want to audit is implied; no environment variables or headers are declared.
Before you install
OAuth grants the server access to your advertising account data, which is sent to a third-party service. Read-only versus write access is not stated, so confirm before letting an assistant change campaigns or budgets.

Installation

In SourceWeft

  1. Open TrueClicks in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.trueclicks%2Ftrueclicks/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "trueclicks": {
      "type": "http",
      "url": "https://data.trueclicks.com/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

56% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.