Generate and edit AI images and video on SayMaker: Veo 3.1, Kling 3.0, Seedance 2.0, Nano Banana 2.
Run SayMaker's image and video models from any MCP client — Claude, Cursor, Cline, Codex. Ask for a picture or a clip in chat, get the file back.
One credit balance covers the whole shelf: Veo 3.1, Kling 3.0, Seedance 2.0 and 2.5, Nano Banana 2, GPT Image 2.5, Seedream 5.0, Qwen Image 3, MiniMax H3, LTX 2.5, Wan 3.0 and more. Every run reports the exact credit cost it charged, and a run that fails for a technical reason is refunded.
| Tool | What it does |
|---|---|
list_models | Every image and video model, and the input each one takes |
generate_image | Text to image, with aspect ratio and resolution |
edit_image | Change one thing in a photo and keep the rest |
generate_video | Text to video, or animate a still you pass in |
get_task | Poll a run submitted with wait: false |
open_in_saymaker | The URL to carry on in the browser |
npx saymaker-mcp
{
"mcpServers": {
"saymaker": {
"command": "npx",
"args": ["-y", "saymaker-mcp"],
"env": { "SAYMAKER_API_KEY": "sk-..." }
}
}
}
Point the client at npx -y saymaker-mcp (stdio transport) and set SAYMAKER_API_KEY in its environment.
Create one at saymaker.ai/settings/apikeys. A key runs on your own account: same models, same credit prices, same plan, and the runs land in your library at saymaker.ai/history.
Without a key the server still starts and runs on the signed-out free wallet, which covers one text-to-image run per browser-sized wallet and is capped per machine per day. Video and the paid image models need a key.
generate_video returns a task id by default. Pass wait: true to block, or poll with get_task.SAYMAKER_BASE_URL overrides the endpoint; only useful when testing against a local build of the site.MIT licensed. Made by SayMaker — the AI video generator agent: say the result, it runs the steps.
Source-derived launch command. Check the maintainer’s required arguments and credentials before running:
npx -y saymaker-mcpMerge this template into ~/Library/Application Support/Claude/claude_desktop_config.json. Keep existing servers. Add any arguments, credentials, and permissions required by the maintainer; this template has not been install-tested.
{
"mcpServers": {
"ai-saymaker-saymaker-mcp": {
"command": "npx",
"args": [
"-y",
"saymaker-mcp"
]
}
}
}Restart Claude Desktop completely for changes to take effect. Confirm the server appears connected in the client’s tool list, then try a read-only example from its documentation.
Claude Desktop setup referencesaymaker-mcpnpmai.saymaker/saymaker-mcp works with any MCP-compatible client. Copy the config snippet from the Configuration section above and add it to the file shown for your client, then restart the application.
~/Library/Application Support/Claude/claude_desktop_config.jsonRestart Claude Desktop completely for changes to take effect.~/.cursor/mcp.jsonRestart Cursor for changes to take effect..vscode/mcp.jsonReload VS Code window for changes to take effect.~/.codeium/windsurf/mcp_config.jsonRestart Windsurf for changes to take effect..mcp.jsonSave at the project root, then start Claude Code in that project and review the MCP server approval prompt. Keep real credentials out of shared files.