NativeAds

ai.nativeadsPublished by nativeads.aiOfficial publisherv1.0.0Updated Oct 24, 2026

AI ad creative generation: brands, Brand DNA, asset uploads, image and video generation.

VerifiedStreamable HTTPWeb executableMedia & Design

Overview

AI-generated overview

NativeAds is a remote MCP server for AI ad creative generation, covering brands, Brand DNA, asset uploads, and image and video generation.

What you can do
Manage brands and Brand DNA that guide creative output. Upload and manage creative assets. Generate ad images and videos from those inputs. The manifest lists no individual tools, so exact operations are not documented here.
When to use it
Useful when an assistant should help produce advertising creatives — brand setup, asset handling, and image or video generation — from within a chat session, without a local install.
Requirements
A remote MCP endpoint reached over streamable HTTP; no local package or runtime is needed. Authentication is OAuth and required, so the user must sign in and authorize access.
Before you install
Access is granted through OAuth to an account on a third-party advertising service, and uploaded assets and brand data are sent to that service. Generation may consume paid credits or quota; check the provider's terms before use.

Installation

In SourceWeft

  1. Open NativeAds 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/ai.nativeads%2Fmcp/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": {
    "nativeads": {
      "type": "http",
      "url": "https://mcp.nativeads.ai/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.