Wevi as a connector

Besides the local @wevi/mcp package, Wevi runs a hosted MCP server at:

https://mcp.wevi.ai/mcp

Clients that support remote MCP servers can connect to it directly. You sign in with your Wevi account in the browser; there is no API key to copy.

Claude

Open Claude → Settings → Connectors → Add custom connector.
Name it Wevi and paste https://mcp.wevi.ai/mcp.
Claude opens a Wevi page asking you to allow the connection. Click Allow.
Back in Claude, enable the Wevi connector in a chat and ask for a video.

Works in Claude on the web and in Claude Desktop on Pro, Max, Team and Enterprise plans.

ChatGPT

Enable Developer mode under Settings → Apps & Connectors.
Add a connector with the URL https://mcp.wevi.ai/mcp and choose OAuth.
Approve the connection on the Wevi page that opens, then use the Wevi app in a chat.

Other MCP clients

Any client that supports the Streamable HTTP transport with OAuth can use the same URL. Clients that only support bearer tokens can send a Wevi API key as the bearer token instead.

The consent page lists it: browse your published templates, create projects and render videos, spend your API & MCP credits, and read render status. It cannot change your plan, billing, or account settings.

Managing a connection

Each connector shows up under Profile → API Keys & MCP as a key named after the app, for example "Claude (connector)".
Its usage and credits appear there like any other key.
Revoke it to disconnect. The app loses access immediately and has to be reconnected.
Connectors always run as live keys and spend credits. Use the local package with a wevi_test_ key for free sandbox testing.

For developers: the OAuth details

Wevi is an OAuth 2.1 authorization server with PKCE and dynamic client registration.

Item	Value
Discovery	`https://api-v2.wevi.ai/.well-known/oauth-authorization-server`
Protected resource metadata	`https://mcp.wevi.ai/.well-known/oauth-protected-resource`
Registration	`POST /api/v2/oauth/register` (RFC 7591, public clients)
Authorize	`GET /api/v2/oauth/authorize` with `code_challenge_method=S256`
Token	`POST /api/v2/oauth/token`, grants `authorization_code` and `refresh_token`
Revoke	`POST /api/v2/oauth/revoke`
Access tokens	Expire after 1 hour; refresh tokens rotate and last 30 days
Scope	`wevi`

Redirect URIs must be https, except http://localhost for local tools.

Connectors