
Ad Creative Intelligence
io.github.atul0016Published by GitHub account atul0016v0.1.1Updated Oct 24, 2026
Creative fatigue, winning-angle, competitor ad, and hook benchmark intelligence.
Overview
A local MCP server that gives an assistant ad-creative intelligence: creative fatigue, winning angles, competitor ads and hook benchmarks.
- What you can do
- Provides ad-creative intelligence on creative fatigue, winning angles, competitor ads and hook benchmarks, so an assistant can discuss and compare creative performance themes. No individual tools are listed in the manifest, so the exact operations are not documented here. It runs as a local process over stdio and requires a purchased license key to start.
- When to use it
- Consider it when you work on advertising creative strategy and want an assistant to help reason about creative fatigue, winning angles, competitor ads or hook benchmarks. It is not a general-purpose tool and is gated behind a paid license.
- Requirements
- Runs locally over stdio, launched with uvx from the PyPI package or from the Docker image. Requires a license key in EARNALL_MCP_LICENSE_KEY, obtained from the vendor's purchase page. Optional EARNALL_MCP_ACTIVATION_ID and EARNALL_MCP_LICENSE_API variables configure the install ID and license validation endpoint. Network access is needed for license validation.
Installation
In SourceWeft
- Open Ad Creative Intelligence in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Tools
0Version history
1- v0.1.1LatestSep 16, 2026
Score
25% 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 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- 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.
- License10 pts
Declare a license in the repository or the registry entry.