Lulu Ads — Publisher Concierge MCP Server

Self-serve publisher onboarding for Lulu Ads. 70% CPA, disclosed sponsored field.

Remote serverstreamable-httpPython

What is the Lulu Ads — Publisher Concierge MCP server?

Self-serve publisher onboarding for Lulu Ads. 70% CPA, disclosed sponsored field. The lulu ads — publisher concierge mcp server wraps that behind the Model Context Protocol, so an assistant can use it through 5 defined tools rather than through you.

What it actually does

70% to publishers · CPA only · 800ms fail-open · 0 prompt injections, by design

Its toolset

Everything the assistant can do here goes through one of these:

  • New — ** enable_lulu_ads() (Python) / enableLuluAds() (TS) — one
  • Stack — One-liner
  • Guarantee — How
  • Quality-gated — every creative passes Dali scoring (≥70) before it can fill a slot
  • Logos — logo takes a URL to fetch a brand mark from, not a URL to embed directly — pass it and the SDK downloads the image right there at registration

Configuration

You will need 2 environment variables: LULU_ADS_PUBLISHER_ID, LULU_ADS_API_KEY. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Adding it to your client

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

When to reach for it

Plenty of developer tooling servers cover similar ground. The differences that matter in practice are scope of access and how much setup stands between you and a working tool call. Lulu Ads — Publisher Concierge's toolset — New, Stack, Guarantee and 2 more — is a fair guide to whether it matches your workflow. It is maintained by Lulu-The-Narwhal; worth a glance at recent repository activity before you build anything load-bearing on it.

SyncDev reviews every entry in this directory against the project's own documentation before publishing, and revisits them as servers change.

Caveats

  • Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • MCP clients confirm each tool call by default. Leave that on until you have watched what the lulu ads — publisher concierge mcp server does with a few real requests.

Available tools

ToolWhat it does
New** enable_lulu_ads() (Python) / enableLuluAds() (TS) — one
StackOne-liner
GuaranteeHow
Quality-gatedevery creative passes [Dali](https://dali.getlulu.dev) scoring (≥70) before it can fill a slot
Logoslogo takes a URL to **fetch a brand mark from**, not a URL to embed directly — pass it and the SDK downloads the image right there at registration time and inlines it into the widget as a data: URI. This isn't incidental

How to install the Lulu Ads — Publisher Concierge MCP server

{
  "mcpServers": {
    "lulu-ads": {
      "command": "npx",
      "args": ["-y", "lulu-ads"],
      "env": {
        "LULU_ADS_PUBLISHER_ID": "your-value",
        "LULU_ADS_API_KEY": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

VariableDescriptionRequired
LULU_ADS_PUBLISHER_IDConfiguration value read at startup.Optional
LULU_ADS_API_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use Lulu Ads — Publisher Concierge to New.
  • Use Lulu Ads — Publisher Concierge to Stack.
  • Use Lulu Ads — Publisher Concierge to Guarantee.

Frequently asked questions

It connects Lulu Ads — Publisher Concierge to MCP-compatible AI assistants such as Claude and Cursor, exposing 5 tools (New, Stack, Guarantee, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Lulu Ads — Publisher Concierge directly.