Connect NewWave to Claude, ChatGPT, Le Chat, or any other AI assistant that supports connectors. Step-by-step setup, what the assistant can and cannot do, and prompts to start with.
Use NewWave from the AI assistant you already have open. Connect it once, then ask for a campaign brief, a shortlist of applicants, or last week’s numbers in plain language. The assistant does the work inside your own NewWave account, with your own permissions.
New to connectors? A connector is a secure link between an AI assistant and an app you use. You paste one NewWave address into your assistant, sign in the way you always do, and approve the connection. There is nothing to install and nothing to run on your computer.
Plan
Research what is working right now, then turn it into briefs and scripts.
Operate
Draft campaigns, review applicants and content, prepare creator messages.
Measure
Pull views, spend, CPM, engagement, and creator performance.
Brands, agencies, and anyone working inside a workspace use this one:
Brands and agencies
https://api.new-wave.ai/mcp
Creators use this one instead:
Creators
https://api.new-wave.ai/mcp/creator
Both use the same NewWave sign-in. The creator address carries only the tools a creator can actually use, so the assistant spends less time offering things your account would refuse.
NewWave has been submitted to the Claude and ChatGPT connector directories and both listings are in review. Until they go live, you add NewWave yourself by pasting the address above. The directory version carries a smaller set of tools: it leaves out moving money, approving creators and videos, taking a campaign live, and signing contracts. Pasting the address above gives you every tool your account allows.
What the words mean
Word
What it means here
Connector
The link between your assistant and NewWave. Some apps call it an app, a plugin, or an MCP server.
MCP
Model Context Protocol, the shared standard that lets any assistant talk to any app. You never have to think about it beyond pasting the address.
Tool
One thing the assistant can do in NewWave, such as listing your campaigns or drafting a script. Assistants show these in a list once connected.
Read-only
A setting that lets the assistant look things up but never change anything. You choose it when you approve the connection.
Token
A password-like string for apps that cannot open a sign-in window. Most people never need one.
In Claude on web or desktop, go to Customize → Connectors. Older versions of the app put the same screen under Settings → Connectors.On a Team or Enterprise plan, an Organization Owner adds the connector once in Organization settings → Connectors. Everyone else then opens Customize → Connectors and selects Connect.
2
Add a custom connector
Select +, then Add custom connector.
3
Paste the NewWave address
Name it NewWave and paste https://api.new-wave.ai/mcp. Creators paste https://api.new-wave.ai/mcp/creator instead.If you see Advanced settings with an OAuth Client ID and Client Secret, leave both empty. NewWave handles that part for you. Select Add.
4
Sign in and approve
Select Connect. A NewWave page opens, headed Connect Claude to NewWave. Sign in as usual, decide whether to leave Read-only access switched on, then select Allow access.
5
Switch it on in a chat
Start a new chat, open the + menu next to the message box, and turn NewWave on for that conversation. Claude lists the read-only tools separately from the ones that change things, so you can allow only what you want.
Free plans allow one custom connector. Pro, Max, Team, and Enterprise plans have no such limit. The connection lives in your Claude account, so once you add it on the web it is there in the desktop and mobile apps too.
Open Settings → Security and login and switch Developer mode on. Some versions keep the same switch under Apps and connectors → Advanced.Developer mode needs a paid plan. On Business, Enterprise, and Education workspaces, an admin may have to allow custom connectors before the switch appears.
2
Create the connection
Open the list of plugins and connectors, then select + to create a new one.
3
Fill in the three fields
Name: NewWave
Description: Run UGC campaigns on NewWave: research, campaigns, creators, submissions, analytics, and payouts. ChatGPT reads this when deciding whether to reach for NewWave, so keep it concrete.
MCP server URL: https://api.new-wave.ai/mcp, including the /mcp at the end. Creators use https://api.new-wave.ai/mcp/creator.
Choose the public endpoint option rather than a tunnel, then create the connection.
4
Sign in and approve
ChatGPT opens NewWave’s approval page. Sign in, choose whether to keep Read-only access on, and select Allow access. ChatGPT then shows the list of tools it found.
5
Switch it on in a chat
Turn NewWave on from the tools menu next to the message box, then ask a read-only question first.
In the sidebar, open Intelligence → Connectors, then select Add Connector and the Custom MCP Connector tab.
2
Paste the NewWave address
Name it NewWave and use https://api.new-wave.ai/mcp as the server URL. Creators use https://api.new-wave.ai/mcp/creator.
3
Choose how to sign in
If Le Chat offers to sign you in to NewWave, take that option and approve the connection on the page that opens.If it asks for an API token instead, create one first in MCP tokens and paste it there.
4
Switch it on in a chat
Select Connect, then pick NewWave from the tools dropdown in a conversation.
claude mcp add --transport http newwave https://api.new-wave.ai/mcp --scope user
--scope user makes NewWave available in all of your projects. Use --scope project to share it with a repo through .mcp.json, or drop the flag for the current project only. Creators point the same command at https://api.new-wave.ai/mcp/creator.
2
Authenticate
Run /mcp inside Claude Code, choose newwave, and select Authenticate. Your browser opens NewWave’s approval page. Approve it and return to the terminal.From a shell, claude mcp login newwave does the same, and claude mcp login newwave --no-browser covers a machine with no browser.
3
Confirm
claude mcp list
NewWave should report as connected.
For CI or a shared machine, skip the browser and use a token:
Open Cursor’s settings, find newwave in the MCP server list, and start the sign-in. Approve the NewWave page that opens; the server then shows as active with its tools listed.
3
Ask in agent mode
Switch the chat to agent mode so tools are available, then name the workspace or campaign you want to work on.
Run MCP: Add Server from the command palette, choose the HTTP option, paste https://api.new-wave.ai/mcp, name it newwave, and pick Workspace or Global.Editing the file directly works too. Workspace settings live in .vscode/mcp.json, and the user-level file opens with MCP: Open User Configuration:
Use this when the client cannot open a sign-in window, such as a script or a server-side agent.
Field names vary a little between apps. Windsurf calls the address serverUrl and wants "type": "streamable-http" next to it, Zed keeps servers under context_servers, and Codex CLI adds one with codex mcp add newwave --url https://api.new-wave.ai/mcp. Check your app’s own MCP page if a key looks different.For anyone wiring this up by hand: NewWave uses OAuth 2.1 authorization code with PKCE and dynamic client registration, publishes its metadata at https://api.new-wave.ai/.well-known/oauth-protected-resource, and supports the scopes full and read.
Most apps keep connectors switched off in each new chat, so start by turning NewWave on. Look for a tools, plugins, or + menu next to the message box.Then ask for something read-only:
Start here
Using NewWave, list my live campaigns and summarize the last 7 days of views, spend, CPM, and videos published. Use NewWave analytics for every number. Do not change anything.
Once that looks right, let it prepare real work for you to approve:
Brands
Using NewWave, review the applicants for [CAMPAIGN]. Rank the strongest five by campaign fit and recent performance, explain each recommendation, and flag anything I should verify. Do not approve, reject, or message anyone yet.
Creators
Using NewWave, show me my active campaigns, what each one still needs from me, and anything blocking a submission or a payout. Explain what to do next, but do not submit or withdraw anything.
Good requests name three things: the workspace or campaign, the outcome you want, and whether the assistant may make changes or should only show you a draft first. The prompt library has longer examples for campaign creation, reporting, and optimization.
The assistant acts as you. It sees and changes only what your NewWave role already allows, and every request runs through the same checks the app uses.
On the brand address, product rules come from the same documentation you are reading now.
Workspace facts come from your live NewWave account.
Numbers come from NewWave’s own reporting rather than the assistant’s arithmetic.
NewWave tells the assistant to ask you first before anything creator-facing or money-moving, but NewWave does not pause the action itself. For a hard stop, use your app’s own approval prompt or choose Read-only access.
Choosing Read-only access when you approve the connection blocks every change at the source. The assistant can still research, report, and draft.
Disconnect at any time in Settings → MCP tokens in the app. Each connected app appears there by name, and revoking it ends that app’s access immediately.
Treat a connector like access to your NewWave account. Only connect assistants you trust, and disconnect the ones you no longer use.
Most apps sign you in and need nothing else. A few, and anything you script yourself, ask for a token instead.
1
Open MCP tokens
In app.new-wave.ai, open Settings → MCP tokens. Brands and creators both have this tab. A token belongs to you, not to a workspace.
2
Create it
Give it a name you will recognize later, pick an expiry of 30 days, 90 days, 1 year, or no expiry, and choose Full access or Read-only.
3
Copy it once
The token appears a single time and starts with nw_mcp_. Store it like any other password, and give it to the app as Authorization: Bearer nw_mcp_....
A read-only token turns down anything that would change data and says so plainly in its answer. Signing in from an app also creates an entry on this same list, named after the app with (OAuth) after it, valid for 90 days. That is where you go to disconnect it.
A connection is good for 90 days, then it asks again. Reconnect from the app. Also check Settings → MCP tokens for an entry you revoked earlier, since a revoked connection always sends the app back to the sign-in page.
No NewWave tools appear in the chat
Most apps keep connectors off in each new conversation. Open the tools or + menu next to the message box and switch NewWave on. Then check that the connection shows as connected in settings, that developer mode is still on in ChatGPT, and that Copilot Chat is in Agent mode in VS Code.
It says it cannot make changes
The connection was approved with Read-only access, or it is using a read-only token. Reconnect with that setting off, or create a full-access token in Settings → MCP tokens.
A creator sees no campaigns
This is almost always the account gate rather than a bug. Ask the assistant to check your waitlist status first. While marketplace access is still pending there is nothing to browse, so the campaign list looks empty either way.
It worked on the wrong workspace or campaign
Name the workspace and campaign in your request. When several could match, ask the assistant to list what it found and wait for your confirmation before acting.
The numbers do not match my dashboard
Ask the assistant to take every number from NewWave analytics. Then check whether you are comparing a live estimate against settled earnings, which stay different figures until the view-accumulation window closes. See how tracking and payouts work.
Something else went wrong
Email support@new-wave.ai with the app you were using, the address you pasted, and what the assistant said back.