Marketing
agentpixel.io
Handles account signup, email confirmation, API key creation, and checks tracking pixel/tag installation status for a marketing platform.
ENDPOINT 1
https://agentpixel.io/mcp
MCP server metadata
- Name
- AgentPixel
- Version
- 1.30.0
AgentPixel - track consented visitors on a site and resolve them to identity records. Getting a free API key (no credit card required): 1. Call signup_free(email, display_name) - starts a 30-day trial without a card and sends a confirmation email. After trial: $1 per account/month. Includes 3 pixels and 500 new contacts per UTC calendar month. No extra charges. New resolution pauses after trial expiry until subscribed; reaching the monthly limit pauses new resolution until the next UTC calendar month. Subscribing does not raise that limit. 2. Open the confirmation link from the email and copy the token from the URL (?token=...). 3. Call confirm_signup(verification_token) with that token - activates the account. 4. Call create_api_key(account_id, signup_token) - returns your API key. Store it securely. Once you have a key, attach it as Authorization: Bearer <key> or X-API-Key: <key> on future connections. Both use the same account validation. The key belongs to the connection - do not pass it as a tool argument. With a key: - whoami: check account status and plan - setup_status: whether a tag is installed on your site - create_pixel(domain): get a pixel id and HTML snippet to install on that site - list_pixels: see all your pixels - check_install(pixel_id): verify the tag is on the homepage - get_contacts(pixel_id, on=...) or get_contacts(pixel_id, after=...): pull resolved contacts create_pixel does not create a new API key - it creates a pixel (tracking tag) for a domain. Errors are tool errors with an HTTP code: 400 fix arguments; 401 use a valid private connection key; 403 follow the account or evaluator next action; 404 use a pixel on your own account; 409 resolve conflicting registration; 429 wait before retrying; 502/503 retry later with bounded backoff. Do not blindly retry signup or key issuance because they can send email or issue another key. Evaluator connections are permanently isolated: synthetic fixtures only, no email, key issuance, payment, live provider or IDGraph. Use staging.allsourcedata.io/evaluation-test/, configure consent, and read synthetic examples after accepted resolution consent. Evaluation is labeled in responses. It is not proof of live identity resolution.
Known tools 12
create_pixelCreate a pixel for a domain and return the HTML snippet to paste on that site.
Potential side effectsCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.agentpixel]
url = "https://agentpixel.io/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"agentpixel": {
"type": "http",
"url": "https://agentpixel.io/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: agentpixel
Remote MCP URL: https://agentpixel.io/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"agentpixel": {
"url": "https://agentpixel.io/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"agentpixel": {
"type": "http",
"url": "https://agentpixel.io/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "agentpixel",
"transport": "streamable-http",
"url": "https://agentpixel.io/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.