Make ads & videosin Claude Code with Adwright

It's Adwright inside your AI assistant. Connect it once and ask in a chat: it researches a product link, makes image ads and video ads in your brand, asks the Ad Council which angle to run, and shows your projects and credits, all in your own Adwright account. MCP (the Model Context Protocol) is the open standard assistants use to connect to apps like this.

ChatGPT, Claude, Claude Code, Cursor, VS Code and Codex, and any other assistant or editor that connects to remote MCP servers with OAuth (the address is https://api.adwright.co/v1/mcp). In a terminal there's also the Adwright command-line tool: npx adwright login.

No. It uses your plan's credits at the same prices as the app, and nothing more: looking at projects, styles and credits is free, and making ads, videos or asking the council costs what it costs in Adwright. Your assistant says what it's about to make before it makes it.

What you allow on Adwright's consent page: your projects (their research, ads and videos), starting projects, making ads and videos, asking the Ad Council and your credits. It never sees your password or payment details, can't change your plan or settings, and can't launch ads or spend ad money: that stays in the app.

Yes. The first time you connect, Adwright opens in your browser to sign in (or sign up), then asks you to allow the assistant. Making ads needs a plan or a trial with credits, as it does in the app.

In Settings, under Sign-in & security, each assistant is listed like a signed-in device: sign it out and it stops working straight away. You can also remove it from the assistant's own settings.