# SeedViews Muse connector

From musedirectory.ai, the independent directory of Meta Muse connectors. Not affiliated with Meta.

## SeedViews

Draft paid creator castings for your app and approve them before anyone is contacted

- Record: https://musedirectory.ai/connector/seedviews
- Category: Marketing & Ads
- Developer: seedviews.com
- Muse status: Extra setup. Not in Muse's Connectors list yet. Muse can still use it: its page gives you a request to paste into Muse.
- Health: Working, 391ms, checked 2026-11-22T18:01:03Z
- Endpoint: https://api.seedviews.com/mcp
- Auth: No account needed; Pricing: unknown
- Screening: Screened, no issues found (2026-11-22T02:46:07Z)
- Source: Found in the official MCP Registry (com.seedviews/seedviews) https://registry.modelcontextprotocol.io/v0/servers?search=com.seedviews%2Fseedviews

Connects to SeedViews to draft UGC creator castings from an App Store or Google Play link. Muse can preview the brief, price and timeline, then send offers, check posted videos, approve payouts and pull the final files once you approve each step.

Example request: "Draft a casting for three creators to film my app and show me the cost before anything goes out."

How to connect: Not in Muse's Connectors list yet, but Muse can still use it. Paste this into Muse: "Use SeedViews to help me. It is a free service with an MCP server at https://api.seedviews.com/mcp. It does not need an API key. Ask me before you share anything with it." Muse asks before it shares anything with the app's site. Meta does not review apps used this way, so only use ones you trust. We tested this in the Muse app on September 24, 2026: Muse used an app's link directly this way and returned a live answer.

Tools:
- cast: Start a casting: real creators film the app and post it on their own accounts. With dry_run: true nothing is saved and nobody is contacted; you get who SeedViews will look for, the brief, the opening message (opening_message_preview), the price, the totals and the timeline to sho
- send_offers: Approves the brief and the opening message together, so outreach starts: SeedViews begins messaging real creators and sending them the paid offer. This reaches real people; confirm the brief and opening_message_preview with your person first. Optional brief, looking_for and openi
- check_video: Without approve, only reads a video's check and approval state (is the post live on the creator's own account, when it counts as approved). approve: true approves it, which lets the creator be paid from money already collected. approve: false needs reason and sends the video back
- pay_creator: Approves one creator payout. The money comes from what was already collected for the casting; the creator is then paid automatically. This moves money: ask your person first unless they told you not to.
- get_results: Reads the casting: status, the opening message, each creator and their state (found, contacted, replied, signed, filming, posted, checked, paid, passed) with our first message to them, each video with views and cost per 1,000 views, totals, and needs_person (what a human must do 
- get_files: Lists the original file of every approved or paid video, with its post link and the ad-rights line (12 months from the post date, final video only). Read only.

Screening checks:
- MCP handshake: pass (Answered in 391ms)
- Domain against threat feeds (Cloudflare security DNS): pass (api.seedviews.com not flagged)
- Published packages against the OSV malicious-package database: n/a (No npm or PyPI package published)
- Hidden instructions or invisible characters in tool text: pass (6 tools read, nothing found)
- Inputs asking for passwords, card numbers or seed phrases: pass (None found)
- Domain and redirects: pass (No redirects off the domain)
- AI review of purpose and tool behavior: pass (spends money and messages real creators; payment link works without sign-in)
