AgentPixel

npx add-mcp 'https://agentpixel.io/mcp'

Connect AgentPixel to your agent

Set up a consent-aware website pixel and read your account's stored contacts through 14 MCP tools. New here? Ask your agent to call try_sample first.

30-day trial without a card, then $1 per account/month. Includes 3 pixels and 500 new contacts per UTC calendar month. No extra charges. New resolution pauses when the trial expires until subscribed. At the monthly contact limit, new resolution pauses until the next UTC calendar month; subscribing does not raise this limit.

1. Choose your client

➜ Ready: add the public server, then review it in your client.

Cursor

Add to Cursor

Requires Cursor installed on this computer. Cursor asks you to review the configuration. This link contains no API key.

Cursor manual setup and private key

Add https://agentpixel.io/mcp as a remote server. After account setup, keep your key in a private environment variable AGENTPIXEL_API_KEY. Review Cursor's MCP configuration instructions.

{
  "mcpServers": {
    "AgentPixel": {
      "url": "https://agentpixel.io/mcp",
      "headers": {
        "Authorization": "Bearer ${env:AGENTPIXEL_API_KEY}",
        "X-AgentPixel-Source": "cursor"
      }
    }
  }
}

VS Code

Run MCP: Open User Configuration in the command palette and add this remote server:

{
  "servers": {
    "AgentPixel": {
      "type": "http",
      "url": "https://agentpixel.io/mcp",
      "headers": {
        "X-AgentPixel-Source": "vscode"
      }
    }
  }
}

Use a supported user or workspace configuration. Review VS Code's MCP instructions.

Add the private key after account setup

This VS Code configuration asks for the key in a masked local input. Agent Host sessions may require a different private environment configuration; review the linked client instructions. Never commit a real key to a repository.

{
  "inputs": [
    {
      "id": "agentpixel-key",
      "type": "promptString",
      "description": "Your private AgentPixel API key",
      "password": true
    }
  ],
  "servers": {
    "AgentPixel": {
      "type": "http",
      "url": "https://agentpixel.io/mcp",
      "headers": {
        "Authorization": "Bearer ${input:agentpixel-key}",
        "X-AgentPixel-Source": "vscode"
      }
    }
  }
}

Cline and Lovable manual connections

Cline

Open Cline MCP Servers, choose Remote Servers, enter AgentPixel and https://agentpixel.io/mcp, choose Streamable HTTP and review the server. After account setup, add your private Bearer authorization through the client configuration, never this website. Official Cline instructions.

{
  "mcpServers": {
    "AgentPixel": {
      "type": "streamableHttp",
      "url": "https://agentpixel.io/mcp",
      "headers": {
        "X-AgentPixel-Source": "cline"
      },
      "disabled": false,
      "autoApprove": []
    }
  }
}

Lovable

Open Connectors, add a custom MCP server and use https://agentpixel.io/mcp. Choose no authentication only for public discovery/signup. For account tools select Bearer token or API key and provide your own confirmed key privately in Lovable. Customer MCP OAuth supports dynamic client registration and S256 PKCE. Client interoperability must still be checked in your client; actual Claude verification and directory approval remain pending. Official Lovable instructions.

These are documented manual setup paths, not verified native installs or marketplace listings.

○ Client installation is not confirmed by this page.

Download portable plugin bundle

Direct file download. Review it in your compatible agent before installing. This is not marketplace approval.

Other clients

Claude Code

claude mcp add --transport http agentpixel https://agentpixel.io/mcp --header "X-AgentPixel-Source: claude_code"

Run it in a terminal, then ask Claude: "Add a consent-first AgentPixel to my site."

Gemini CLI

gemini extensions install https://github.com/byron-allsourcedata/agentpixel-mcp

Then ask Gemini to start an AgentPixel trial for your email.

Any other MCP client: add https://agentpixel.io/mcp as a streamable HTTP server. Optional: add ?src=<where you found us> to the URL.

2. Set up your account

➜ Ready: ask your connected agent to start your trial.

1. Use signup_free(email, display_name) with your own details. Keep its account ID and private signup token.
2. Read the 6-digit code in the AgentPixel email to your agent. It calls confirm_signup(account_id, code, signup_token), which returns your API key. Store the key privately in your client.
3. If you clicked the email link instead, the agent checks with confirm_signup(account_id, signup_token) and then calls create_api_key(account_id, signup_token).
4. Use whoami() and setup_status() to check account access. The operator console password is separate from this customer API key.

Codes and signup tokens last 24 hours. If a code expired or an email did not arrive, ask the agent to call resend_code(email). For anything else, follow signup recovery instructions. Do not repeat signup or key issuance blindly.

For a client that supports dynamic registration and S256 PKCE, connect the MCP URL and follow the AgentPixel account authorization screen. New to AgentPixel? That screen starts a 30-day trial, no card: enter your email, type the 6-digit code, then approve. Existing accounts sign in with their private AgentPixel API key. Review the requesting client and permissions before approval. Existing private-key connections remain available. Actual Claude connector verification and directory approval remain pending. The public MCP URL can be inspected without a key; Virgil operator sign-in is separate from customer connector authorization.

3. Choose your task

➜ Ready: follow one guide for a site and account you control.

• Identify consented website visitors with MCP
• Install and verify a consent-aware website pixel
• Read consented website contacts with an MCP cursor
• How to add a website pixel with Claude Code
• How to add a tracking pixel to your site in Cursor
• How to identify website visitors with consent

Publishing a tag is separate from verified installation. Stored contacts are separate from traffic, and identification is never guaranteed.

Discovery and measurement details

Machine-readable connection catalog, agent reading map, server registry manifest. We count anonymous page requests and link/configuration actions as best-effort metadata, including bots and operator checks. These are not unique users, confirmed installs or provider impressions. No key, contact payload, email, IP or browser identifier is stored in this connection-event telemetry.