Notch
ai.usenotchPublished by usenotch.aiOfficial publisherv1.0.1Updated Oct 24, 2026
Turn product pages and creative briefs into finished video and image ads from your AI chat.
Overview
Notch turns product pages and creative briefs into finished video and image ads from an AI chat, via a remote MCP endpoint.
- What you can do
- Generate finished video ads from product pages or creative briefs supplied in chat. Produce image ads from the same inputs. Work from a product page or a brief rather than from raw media assets. The manifest lists no individual tools, so the exact operations are not documented here.
- When to use it
- Useful when you want ad creatives drafted or produced inside an AI chat session without leaving it for a separate design tool, especially for product-based campaigns.
- Requirements
- A remote MCP endpoint at app.usenotch.ai over streamable HTTP; no packages, environment variables or headers are declared. The manifest declares no authentication, so check the provider's setup page for how access is granted.
Installation
In SourceWeft
- Open Notch in the dashboard and add it to a workspace.
- 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.usenotch%2Fnotch/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.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"notch": {
"type": "http",
"url": "https://app.usenotch.ai/mcp"
}
}
}Tools
0Version history
1- v1.0.1LatestSep 16, 2026
Score
17% 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
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declaredRequired10 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
Publish an icon in the registry entry.
- 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.
