Integration

Proofly integration

Proofly shows social proof notifications (recent sign-ups, purchases, visitor counts) on websites. Read the account's user details and activity log, list campaigns and the notifications inside each campaign with their impressions, hovers, clicks and leads, read the leads and conversions a notification collected, and switch a campaign on or off. Creating or editing campaigns and notifications is done in the Proofly dashboard. Authentication is an API key sent in the X-Api-Key header; free accounts may send 10 requests per minute, paid accounts are not rate limited.

Connect Proofly How integrations work

Ask it in chat

Say what should happen.
The workflow builds itself.

When this happens, do that in Proofly.Built from the 6 Proofly tools below, on the connection you add once.

What you can do with Proofly

Each of these is one operation on one endpoint, available both as a workflow step and as a tool an AI agent can call on its own. Nothing bundles several operations into one action, so what a run did stays readable afterwards.

Most endpoints run on the free plan. A few, mainly the ones that publish on your behalf, need a paid plan.

Campaign, 2 operations

list_campaignsList campaignsGETReturns every campaign in the account with its id, name, domain (and whether subdomains are included), enabled flag and creation date. Use the id with list_campaign_notifications.
toggle_campaignToggle campaignPUTFlips a campaign between active and inactive (enabled becomes disabled and the reverse). Takes no body. Read enabled in list_campaigns first to know which way it will go.

Activity, 1 operation

list_activityList activityGETReturns the account's activity log: each entry has a type (for example login.success or register.success), the IP address and the date.

Lead, 1 operation

list_notification_dataList notification dataGETReturns the data, leads and conversions one notification recorded: each item has a type (for example collector), the captured input, IP, page URL, visitor location and date.

Notification, 1 operation

list_campaign_notificationsList campaign notificationsGETLists the notifications of one campaign: id, name, type, trigger and display settings, stats (impressions, hovers, clicks, leads) and enabled flag. Pass an id to list_notification_data.

User, 1 operation

get_userGet userGETReturns the account holder's name, email, login count, registration date, impressions (current period and total) and pixel debug flag.

Use Proofly from Claude Code, Cursor or Codex

Connect Proofly in LiveContext, create an API key in Settings, then add the LiveContext MCP server to your client. Its Proofly operations become tools the client can call, next to every other integration you connected.

Claude Code

claude mcp add --transport http livecontext https://livecontext.ai/mcp --header "X-API-Key: YOUR_API_KEY"

Codex (~/.codex/config.toml)

[mcp_servers.livecontext]
url = "https://livecontext.ai/mcp"

[mcp_servers.livecontext.http_headers]
"X-API-Key" = "YOUR_API_KEY"

Cursor, Claude Desktop and other JSON configs

{
  "mcpServers": {
    "livecontext": {
      "type": "http",
      "url": "https://livecontext.ai/mcp",
      "headers": {
        "X-API-Key": "YOUR_API_KEY"
      }
    }
  }
}

Set up the MCP server step by step

How to connect Proofly

Create your workspace
Sign up free. Nothing to install.
Connect Proofly once
Add your Proofly connection in Settings. Every tool from this integration reuses it, and secrets are encrypted at rest and visible only to you.
Describe the job in chat
The workflow builds itself in front of you and picks the endpoints it needs. Drag the steps yourself on the canvas whenever you would rather be explicit.