
Marketing Content Production
io.github.atul0016Published by GitHub account atul0016v0.1.1Updated Oct 28, 2026
Brand-safe ad, email, product description, and social content production.
Overview
Local MCP server for producing brand-safe ad, email, product description and social marketing content, gated by a paid license key.
- What you can do
- Generate marketing copy for ads, emails, product descriptions and social posts.
- Keep output brand-safe according to the server's built-in rules.
- No tool list is published, so the exact operations are not documented in the manifest.
- Runs as a local stdio process, launched with uvx or the provided Docker image.
- When to use it
- Consider it when you want an assistant to draft marketing copy across several channels and need the output constrained to brand-safe wording. It is a poor fit if you need a documented tool list or a free, no-license setup.
- Requirements
- A local runtime: Python with uvx for the PyPI package, or Docker for the published image. A license key in EARNALL_MCP_LICENSE_KEY, obtained from the vendor's purchase page. Optional EARNALL_MCP_ACTIVATION_ID for a stable install ID and EARNALL_MCP_LICENSE_API to point at a license validation endpoint. Desktop only; no remote endpoint.
Installation
In SourceWeft
- Open Marketing Content Production 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.