estimate_video_cost — Video Generation Cost Estimator MCP Tool
estimate_video_cost
(estimate video cost) is one of 3 tools on the
Video Generation Cost Estimator
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call estimate_video_cost from your client
- Claude Code Video Generation Cost Estimator estimate_video_cost run in your project directory
- Claude Desktop Video Generation Cost Estimator estimate_video_cost ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor Video Generation Cost Estimator estimate_video_cost ~/.cursor/mcp.json
- VS Code Video Generation Cost Estimator estimate_video_cost .vscode/mcp.json
- Zed Video Generation Cost Estimator estimate_video_cost ~/.config/zed/settings.json
- Windsurf Video Generation Cost Estimator estimate_video_cost ~/.codeium/windsurf/mcp_config.json
- Cline Video Generation Cost Estimator estimate_video_cost ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI Video Generation Cost Estimator estimate_video_cost ~/.gemini/settings.json
- Grok Video Generation Cost Estimator estimate_video_cost .mcp.json (in your project root)
- ChatGPT Video Generation Cost Estimator estimate_video_cost Settings → Connectors → Advanced → Developer mode
- Claude.ai Video Generation Cost Estimator estimate_video_cost Settings → Connectors → Add custom connector
- LangChain Video Generation Cost Estimator estimate_video_cost pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http agent-data-platform https://agent-data-platform.onrender.com/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.