Where do I create a Cursor key?

In the Mimelio app: workspace Settings → Claude (not inside a project). Paste the mim_mcp_ key into ~/.cursor/mcp.json. Do not put that key in the Claude.ai connector dialog — Claude uses OAuth.

Can the assistant publish live copy without me?

It should not. Product instructions require a confirm on writes, and status ACTIVE is a separate tool. Treat any agent that skips confirmation as misconfigured.

docs.mimelio.com/how-to/create-segments-with-ai

Not Melio (bill pay). Mimelio personalizes Google Ads landing pages.

Drive Mimelio from your AI assistant (MCP)

Mimelio is a Google Ads landing-page personalization tool. It also ships a remote MCP server scoped to your workspace: an assistant can read keywords, propose intent segments, write draft headline/CTA variants, and set a city fallback — nothing goes live until you confirm.

What this is for

Reading 200 keywords into three visitor intents is tedious. MCP is how Cursor, Claude, and similar agents do that pass inside your Mimelio workspace. They cannot see another organization. Writes are drafts until you activate.

List projects, landing pages, coverage (which keywords have a segment).
Sync Google Ads, then file new keywords into segments.
Propose and apply segments on one landing page at a time.
Write experience copy, including {city} and a geo fallback on Growth/Agency.
Simulate a real Google Ads click URL before you go live.

Sync Google Ads, then file new keywords

Ask the assistant to sync Google Ads and sort new keywords. It starts a manual sync (mimelio_user_sync_google_ads), polls mimelio_user_get_sync_status until the run is done, inspects coverage with mimelio_user_inspect_coverage, then applies a segment (mimelio_user_apply_segment) or moves keywords (mimelio_user_reassign_keywords). Sync only imports keywords — it does not assign them. Manual syncs are limited to 4 times per project per 24 hours because of the shared Google Ads API quota.

Once a day Mimelio syncs projects with Google Ads connected and stores suggestions only for new unassigned keywords in campaigns and ad groups that are already synced and already attached to a segment. The suggestion uses the segments that ad group already uses. The assistant lists them with mimelio_user_list_keyword_suggestions. After you confirm, mimelio_user_resolve_keyword_suggestions accepts (same assignment as mimelio_user_reassign_keywords) or rejects. Nothing is filed until you accept.

What it is not

Not a public unauthenticated API. Not the internal debug MCP used by Mimelio staff. A conversions key (mim_live_) cannot open this server. The assistant must show you the exact copy and wait for confirmation before any write, and activation is a separate step.

Claude (Connectors)

In Claude: Settings → Connectors → Add custom connector.
URL: https://mimelio.onrender.com/v1/mcp — leave OAuth client ID and secret empty; Claude registers itself.
Click Connect, sign in to Mimelio, pick a workspace, Allow.

Cursor

{
  "mcpServers": {
    "mimelio": {
      "url": "https://mimelio.onrender.com/v1/mcp",
      "headers": {
        "Authorization": "Bearer mim_mcp_…"
      }
    }
  }
}

Questions

Where do I create a Cursor key?: In the Mimelio app: workspace Settings → Claude (not inside a project). Paste the mim_mcp_ key into ~/.cursor/mcp.json. Do not put that key in the Claude.ai connector dialog — Claude uses OAuth.
Can the assistant publish live copy without me?: It should not. Product instructions require a confirm on writes, and status ACTIVE is a separate tool. Treat any agent that skips confirmation as misconfigured.
Full setup guide?: docs.mimelio.com/how-to/create-segments-with-ai

Step-by-step: create segments with AI