AgentPixel

io.agentpixelPublished by agentpixel.ioOfficial publisherv0.1.4Updated Oct 24, 2026

Most visitors never fill out a form. Turn the ones who click Accept into contacts your agent reads.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowBusiness & Commerce

Overview

AI-generated overview

AgentPixel is a hosted consent-first website pixel service that lets an assistant set up a pixel, configure a consent bar, verify the tag and read visitor…

What you can do
  • Preview labeled synthetic sample output without an account
  • Sign up for a 30-day trial, confirm the email with a 6-digit code and issue an API key
  • Check account identity, plan, trial end and setup status
  • Create, list and inspect pixels, including the HTML snippet to paste on a site
  • Configure the consent bar, get the hosted policy, and check whether the tag is installed
  • Pull contacts for a pixel by UTC day or by cursor
When to use it
Use it when you own a website and want an assistant to walk through consent-first pixel setup and then read back the contacts of visitors who clicked Accept. It suits marketing or lead-generation follow-up on traffic that never fills out a form.
Requirements
A remote MCP endpoint; no local runtime or package. Public discovery, the sample and signup need no credential. Protected tools need account authorization (OAuth with PKCE) or an API key supplied through the Authorization bearer header or the X-API-Key header. Signup needs an email address that can receive a 6-digit code. A website you control is needed to install the tag.
Before you install
The API key is shown once and must be stored privately; the README warns never to put a real key, signup token or email-confirmation token in a repository, chat or URL. The service is paid after the 30-day trial at $1 per account per month, and the account pauses after trial expiry until subscribed. Tools create pixels, change consent settings (which re-asks returning visitors) and issue new keys. Contact data concerns identified visitors, so consent and privacy handling matter.

Installation

In SourceWeft

  1. Open AgentPixel in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.agentpixel%2Fagentpixel/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "agentpixel": {
      "type": "http",
      "url": "https://agentpixel.io/mcp"
    }
  }
}

README

AgentPixel agent plugin

Most people who visit your website never fill out a form. AgentPixel helps you meet the ones who click Accept.

Why use it

You pay to bring people to your site through ads, content and events, and most of them leave without a name. With AgentPixel, visitors click Accept to be identified, and they come back as contacts, so you can:

  • Follow up with prospects who never filled out a form. Add them to nurture and convert them later.
  • Get more from the ad spend you already have. Paid clicks from visitors who click Accept become contacts, not just anonymous sessions.
  • Know who your traffic really is. Job titles and companies of visitors who click Accept show whether your traffic fits your ideal customer profile.

Every result depends on visitors who click Accept, and not every visitor who clicks Accept can be matched to a contact.

How it works. Consent-first website pixel: set up the consent bar, install the tag, verify it and read contacts. Your AI agent does the setup. It can show labeled sample output with try_sample (no account, no key), start a 30-day trial (no card) with a 6-digit code from your email, install the snippet from configure_consent and read contacts by day. Then $1 per account per month.

Install

[Install in VS Code] [Install in Cursor] [AllMCPs Verified] [M8ven Score]

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

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

This package connects compatible clients to the hosted AgentPixel MCP service and supplies one workflow skill. The backend stays private and hosted. No executables, credentials or customer records are bundled.

Connection and authentication

Endpoint: https://agentpixel.io/mcp. Public discovery and signup need no credential. Protected tools support account OAuth with dynamic client registration and S256 PKCE. When a compatible client offers authorization, use the first-party AgentPixel page to connect your own account. Its masked AgentPixel API key field expects your private account key, not the operator console password. Review the client callback destination and account permissions before approving.

After signup, confirm the email and obtain your account key using the documented onboarding tools. Never put a real key, signup token or email-confirmation token in this package, a public repository, chat or a URL. Direct Authorization: Bearer fallback is available for clients whose documentation supports remote request headers, including Cursor and Cline. Configure it only in private user settings. OAuth protocol and account binding have been tested. Direct public discovery using the client-specific URL configuration below was verified with Cursor CLI 2026.10.01 and returned all 12 tools that existed then (14 today). On 2026-10-10, Cline's MCP client (cline CLI 3.0.70) connected with the llms-install.md configuration, listed all 14 tools and ran try_sample. Plugin installation, account OAuth in Cursor, the native Cursor GUI, a full Cline agent session and marketplace approval remain untested.

The portable mcp.json follows Agent Plugins 1.0.0. Do not copy its root mcp.json directly into native Cursor or Cline settings. The portable streamable-http transport spelling is not their direct settings format; use the client-specific snippets below. Copying the portable configuration directly into native Cursor settings failed discovery in the isolated test. The fixed X-AgentPixel-Source labels are untrusted reported sources, not proof of identity, installation or independent adoption.

Cursor

Follow Cursor's plugin instructions for a compatible Agent Plugin. This package uses root plugin.json, mcp.json and skills/agentpixel/SKILL.md; it is not a marketplace-approved listing.

For a direct hosted connection, use Cursor's documented MCP configuration. Merge this entry into your private user ~/.cursor/mcp.json, preserving existing servers:

json
{  "mcpServers": {    "agentpixel": {      "url": "https://agentpixel.io/mcp",      "headers": {"X-AgentPixel-Source": "cursor"}    }  }}

Use client authorization when offered. For the documented header fallback, add "Authorization": "Bearer ${env:AGENTPIXEL_API_KEY}" to this entry's headers and set your own private environment variable. Confirm the tool list, then use whoami to check the intended account. This URL-based example discovered all 12 tools that existed then (14 today) in an isolated Cursor CLI 2026.10.01 test. That result verifies public discovery only, not plugin installation, account authorization, tool outcomes or the native GUI.

Cline

Follow Cline's remote-server instructions. In the Cline panel, open MCP Servers, Configure, then Configure MCP Servers. Merge this entry into the user's private settings, preserving other entries:

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

Use OAuth authorization when the client offers it. If using Cline's documented header fallback, add "Authorization": "Bearer REPLACE_WITH_YOUR_PRIVATE_ACCOUNT_KEY" to this entry's headers in private settings only. Never commit the replacement value. Leave autoApprove empty and review tool requests. Check that tools appear, then call whoami. Native Cline setup and marketplace acceptance remain untested.

Gemini CLI

The root gemini-extension.json provides the hosted Streamable HTTP connection. Follow Gemini CLI's extension instructions to install:

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

Review the installation prompt and tool requests. Public discovery requires no key. Private account tools require authorization through the client. Keep credentials in private client settings only, never in the repository or chat. The companion skills/agentpixel/SKILL.md describes the website owner and consent workflow. Native Gemini CLI installation, private account authorization and gallery acceptance remain unverified.

Framework integrations

Use AgentPixel from agent frameworks with any MCP client. Minimal examples, including keyless signup and the px_ key:

See docs/integrations for how auth works across frameworks.

Useful tasks

See the public connection guide and API documentation for live schemas and troubleshooting. Registry identifier: io.agentpixel/agentpixel (mcpName in registry package metadata where applicable). This README marker does not prove registry publication or ownership verification; package-type requirements differ.

Pricing

The 30-day trial requires no card. Afterward, service costs $1 per account per month, covering up to 3 pixels and 500 new contacts per UTC calendar month, with no extra usage charges. After trial expiry, the account pauses until subscribed. New resolutions stop at the monthly limit and resume with the next UTC month's allowance. Subscription does not increase that limit. Consult account status and the current contract for available reads and next actions.

License, privacy, terms and support

The distributed connection package, workflow text and wordmark are covered by the MIT License, copyright 2026 AllSource Data Corporation. The license grants no hosted-backend source, service credentials, account access or private AllSource systems. logo.png is a 400x400 text wordmark derived from AgentPixel's existing public brand name and colors; it carries no certification mark.

Website owners supply their controller identity, consent purposes and site policy. Privacy policy: allsourcedata.io/privacy. Terms: allsourcedata.io/terms. Support: [email protected].

Source: README.md at commit 12e6448

Tools

14

try_sample

See sample output

Labeled sample of what an account gets: a pixel, a consent receipt and two contacts. Needs no account and no key. Every record is synthetic and marked so. Call this first to show the person what AgentPixel returns, then call signup_free.

Takes no parameters.

signup_free

Start 30-day trial

Start a 30-day trial, no card. After that, $1 per account per month for 3 pixels and 500 new contacts per UTC calendar month. Sends a 6-digit code to the email address. Returns account_id and signup_token; keep both. Next: ask the person for the 6-digit code in the AgentPixel email, then call confirm_signup(account_id, code, signup_token). The signup_token lasts 24 hours.

Parameterscodeemailrequireddisplay_namerequired

confirm_signup

Confirm signup email

Confirm the email with the 6-digit code, or check whether the email link was clicked. Preferred: confirm_signup(account_id, code, signup_token). The first confirmation returns api_key; store it, it is shown once. Link clicked instead: call confirm_signup(account_id, signup_token) every 5 seconds, up to 10 minutes, until email_verified is true, then call create_api_key. A code allows 5 attempts and lasts 24 hours. For a new code, call resend_code(email).

Parameterscodeaccount_idsignup_tokenverification_token

resend_code

Send a new email code

Send a new 6-digit code to the email of an existing account. Use it when the code expired, was lost or was entered wrong 5 times. Limits: 1 per minute, 5 per day. The old code stops working. With an expired signup_token, use the new code on POST /v1/accounts/{account_id}/signup-token to get a new token.

Parametersemailrequired

create_api_key

Issue private API key

Issue an API key after the email is confirmed. Not needed when confirm_signup already returned api_key. Each call issues another key, so call it once. Returns the key once. Store it securely and attach it to the connection.

Parametersaccount_idrequiredsignup_tokenrequired

whoami

Check account identity

Which account this connection's API key belongs to. status is the account state after email confirmation. plan is "free" (the trial plan id) during the 30-day trial, paid after the subscription, or unlimited for internal accounts. trial_ends_at is when the trial ends. key_prefix is the start of the key, not the key.

Takes no parameters.

setup_status

Read installation progress

Whether this account can use pixels and whether a tag is installed. setup_complete is true once at least one pixel's tag has been seen on its site. good_standing is the account, not the tag.

Takes no parameters.

list_pixels

List my pixels

Pixels on this account. Each item has pixel_id, domain, and install_status.

Takes no parameters.

create_pixel

Create site pixel

Create a pixel for a domain. Does not create an API key. The account must already be active. Next: call configure_consent(pixel_id, controller_name, purposes) and install the snippet it returns. Do not install a snippet before consent is configured. install_status starts as not_checked until check_install runs.

Parametersdomainrequired

get_pixel

Read pixel and install tag

One pixel, including the HTML snippet to paste on its site.

Parameterspixel_idrequired

check_install

Check and save installation

Fetch the pixel's homepage and store whether the tag is there. install_status becomes installed or not_installed. check_error says why a check could not decide. Evaluator accounts fetch only the fixed https://staging.allsourcedata.io/evaluation-test/ page and reject redirects.

Parameterspixel_idrequired

get_policy

Read hosted privacy notice

Hosted privacy and data-use policy HTML for a pixel. A pixel with consent turned off has no policy yet.

Parameterspixel_idrequired

get_contacts

Read contacts

Contacts for one pixel. Pass on as a UTC day, or after as the high_water from the previous pull. Use high_water as the next cursor. New contacts can arrive between reads. This does not identify new visitors. Evaluation returns labeled synthetic examples only after current resolution consent is saved; withdrawal hides them.

Parametersonafterpixel_idrequired

Version history

2
  1. v0.1.4LatestOct 11, 2026
  2. v0.1.1Oct 9, 2026

Score

100% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts