An independent, unofficial guide. Not affiliated with Everygen. Official website: everygen.ai ↗
everygentips

MCP CONNECTION GUIDE

Everygen MCP,
without the guesswork.

A remote connection lets an assistant discover media tools and request work through your Everygen account. Connect first, inspect second, generate only after reviewing the cost.

The connection in plain English

The current public endpoint is https://everygen.ai/api/mcp. Everygen’s developer page documents OAuth 2.1 and per-tool scopes. A generic API-key recipe is not the default documented flow.

Never paste a secret into a prompt.

Use the provider’s authorization screen. This guide and its copy tools do not request or store your credentials.

Choose your client

Claude: connect through the official entry

  1. Open Everygen’s MCP page and select “Add Everygen to Claude”. Alternatively, open the custom connector setup in Claude’s connector settings.
  2. For a manual remote connector, enter https://everygen.ai/api/mcp. Use a name such as “Everygen”.
  3. Follow the Everygen sign-in / OAuth screen and inspect the requested permissions. Team settings may require an administrator.
  4. Enable the connection in your conversation, then ask for the available models and credit information before asking it to create anything.

Remote connectors use the account connection flow. A local Claude Desktop JSON entry is a different mechanism; do not assume a URL-only block works in that file.

Verify before spending

Use the Everygen connection to list available tools, supported video models, and my credit balance if read access permits. Do not upload media or generate anything. Tell me which information is unavailable. Then explain which tool would create a 5-second clip and whether a cost estimate can be obtained without running it.

A connected status is only the first check. Verify that tools are listed, permissions match your intended workflow, and the assistant can explain the next action. If it cannot quote a cost, inspect the settings and quote on the official site before proceeding.

Choose the smallest permission set

Everygen lists distinct read and generation scopes. For discovery, look for generation:read. Creation may require video:generate or image:generate; media import uses media:upload. Voice and audio tools have their own scopes.

For an actual generation, specify the subject, settings, maximum attempts and credit ceiling. Ask the assistant to show its proposed action before executing it. A conversational budget is a workflow instruction, not a guarantee of a server-enforced spending limit.

When the connection fails

SymptomCheckNext step
Unauthorized / 401Expired authorization, wrong account or missing permissions.Disconnect and reconnect through the official OAuth flow.
Forbidden / 403Workspace policy, tool scope or account access.Check administrator restrictions and requested permissions.
No tools appearMCP disabled in the chat, transport mismatch or stale client state.Enable the connection and reload the client; confirm the endpoint.
An endpoint URL fails in a browserMCP is not a normal HTML page.Use a compatible remote MCP client; a browser error alone is not a transport test.
Generation is rejectedPlan, credits, unsupported settings or media restrictions.Read the specific tool error; check the official account and generator quote.

These are diagnostic possibilities, not errors we reproduced. Record the client version and sanitized error; remove tokens, uploaded media URLs and account information before sharing logs.

Sources & verification

The flow diagram above is our own explanatory illustration. We have not published app screenshots or claimed a successful authenticated installation. UI labels can vary; confirm against each linked client guide.