Pixero

io.github.ryanzambranoPublished by GitHub account ryanzambranov1.0.0Updated Oct 24, 2026

AI marketing agent for paid social: Meta ads campaigns, ad creative generation, lead delivery.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Pixero is a remote AI marketing agent for paid social that lets an assistant manage Meta ad campaigns, generate ad creative, and handle lead delivery.

What you can do
Manage Meta ads campaigns through the assistant, including campaign setup and related paid social work as described by the provider. Generate ad creative for paid social advertising. Handle lead delivery from campaigns. The provider lists no individual tools, so exact operations are not documented here.
When to use it
Worth considering when you run paid social advertising on Meta and want an assistant to help with campaign management, creative generation, and lead handling in one place.
Requirements
A remote endpoint at pixero.ai reached over streamable HTTP. OAuth authentication is required, so you need a Pixero account and must complete the OAuth sign-in. No environment variables or headers are declared.
Before you install
OAuth grants the assistant access to your Pixero account and its advertising data. The server can act on live Meta ad campaigns, which may involve spending money and changing or publishing campaign data. Lead data is handled through the service, so consider where that data goes. Review the provider's terms before connecting.

Installation

In SourceWeft

  1. Open Pixero in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. 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.github.ryanzambrano%2Fpixero/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. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "pixero": {
      "type": "http",
      "url": "https://pixero.ai/api/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

67% 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 listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.