AgentPixel

What AgentPixel does

AgentPixel MCP server gives an AI agent a workflow for adding and managing a consent-aware website pixel. The service can help set up a consent bar, install the site tag, check whether consent and tag configuration are correct, and retrieve contacts associated with consenting visitors.

The workflow is intended for website owners and teams that want to follow up with visitors who accepted tracking consent but did not submit a form. Contact matching is not guaranteed for every consenting visitor, and results depend on visitors selecting Accept.

A public sample path is available through try_sample. It returns labeled example output without requiring an account or API key, making it suitable for checking the connection and understanding the response shape before linking a customer account.

How it works

The hosted endpoint is https://agentpixel.io/mcp and uses Streamable HTTP. The repository contains connection metadata and a workflow skill; the backend remains hosted, so the package does not include an executable, credentials, or customer records.

Public discovery and signup do not require credentials. Account-specific operations use OAuth with dynamic client registration and S256 PKCE when the client supports authorization. A direct bearer-token option is also available for clients that support remote request headers. The token must be the private account key, not the password for the operator console.

After signup, the account owner confirms an email and obtains an account key through the documented onboarding flow. The service offers a 30-day trial without a card. After the trial, pricing is $1 per account per month for up to three pixels and 500 new contacts per UTC calendar month; the account pauses after trial expiry until subscribed.

Setup and configuration

The AgentPixel MCP server can be connected directly from clients that support remote MCP servers. The README documents configurations for Cursor and Cline, a Gemini CLI extension installation, and a Claude Code HTTP command. VS Code and Cursor also have installation links. Framework examples are provided for LangChain, LangGraph, CrewAI, Vercel AI SDK, and Mastra.

For a direct connection, configure the hosted URL in the client’s private MCP settings and preserve existing server entries. If using the bearer fallback, store the value in a private environment variable such as AGENTPIXEL_API_KEY; never commit it or place it in a URL. Client-specific configuration formats differ, so the portable mcp.json should not be copied unchanged into native Cursor or Cline settings.

After connecting, confirm that tools are visible and use whoami to check the intended account. Review authorization destinations, permissions, and tool requests before approving them.

Tools and capabilities

Documented capabilities include:

• Running try_sample without an account or key.
• Starting a trial using an emailed six-digit code.
• Configuring a consent bar and obtaining the installation snippet through configure_consent.
• Verifying consent and tag installation.
• Reading contacts by day.
• Retrieving contacts with date-based or cursor-based modes.
• Checking the connected account with whoami.

For cursor retrieval, begin with after: 0. Commit a returned non-null integer cursor only after processing succeeds, then retry from the last committed cursor if necessary. Deduplicate stable identifiers when they are available.

Limitations and notes

The service only identifies visitors who click Accept, and some of those visitors cannot be matched to a contact. Receiving a tag from configuration does not prove that the tag is installed on the website. Date and cursor retrieval are separate modes, and a date query may return high_water: null.

The README reports public discovery tests for Cursor and Cline, while plugin installation, native Cursor GUI use, full Cline agent sessions, Gemini private authorization, and marketplace approval remain unverified. Source labels such as X-AgentPixel-Source identify a reported client source but do not prove identity or adoption. Keep account keys, signup tokens, and email-confirmation tokens out of repositories, chats, and URLs.