By the PopNow team, with AI assistance from OpenAI Codex. This guide is based on PopNow’s public documentation; it does not report a generation test or a performance benchmark.

You can connect a creative service to an assistant without pasting an API key into the conversation. PopNow’s hosted MCP server supports OAuth: the assistant opens a sign-in page, you review the connection, and the client keeps the authorization needed for later tool calls.

The useful first milestone is a verified connection. You do not need to generate a video to find out whether you connected the right account.

1. Start from a client you chose

Use an MCP client that supports Streamable HTTP and OAuth. Availability can depend on the client’s plan, workspace policy, and current version. Follow that client’s current connector instructions rather than assuming a menu path from another app will match.

The PopNow server address is:

https://api.popnow.ai/mcp

This is a hosted endpoint. A compatible client can connect directly; it does not need to install a local server first. PopNow also publishes an optional open-source bridge for clients that need a different connection approach. The bridge and the hosted generation service have different roles, so choose the connection method your client actually supports.

Give the connection a recognizable name, such as “PopNow.” That makes it easier to distinguish the service from a similarly named connector later.

2. Check the account before allowing access

Begin the authorization flow inside the client you intend to use. On the PopNow sign-in and consent pages, check the account shown and the client requesting access. If a browser already has several accounts signed in, the first account offered may not be the one that holds your work.

PopNow’s documented OAuth permissions cover reading account information and creating media. Treat those as meaningful permissions: a connection can be useful for reading a balance, but its creation tools can also spend funds.

If you did not start this connection, stop and return to the client. A familiar service name alone is not a reason to approve an unexpected consent page.

3. Make the first request read-only

After connecting, ask the assistant for a small verification step:

PopNow documents balance and model-list tools as read-only. A successful response is a practical way to confirm that the client can reach the server and access the intended account, without using a paid media-generation call as a connectivity check.

Keep the instruction narrow. “Set everything up” can leave an assistant guessing whether it should make a sample image. A read-only request gives you a result you can inspect before deciding what comes next.

4. Approve the creative request separately

Once the account check is complete, describe the result you want: the subject, format, reference material, and limits that matter. Ask the assistant to look up current model information without calling a generation tool. Some requests can start immediately under the documented automatic-start rules, so a creation call is not a safe substitute for a read-only price check. Review the proposed operation and budget, then authorize creation deliberately.

Connecting with OAuth does not make media generation free. Also check the current billing documentation for the authentication method you use; do not assume that an API-key workflow and an OAuth connection draw from the same balance.

For a first project, use a reference you own or have permission to upload. Confirm the actual model and requested output before starting a costly revision or a longer video.

5. Keep connection ownership clear

A team should decide which account owns a connection and who may authorize spending through it. Avoid passing one person’s connection around as a shared credential. If you switch between personal and work accounts, repeat the read-only account check before creating anything.

When you no longer need the integration, remove or revoke the connection using the service’s connection controls. Do not paste tokens into a support conversation to demonstrate that sign-in worked.

A reliable setup ends with a simple, observable fact: the chosen client can read the intended account. Creation is the next deliberate step.

Sources: PopNow MCP guide, API reference and authentication-specific billing, open-source MCP bridge.