Connectors
Add Wevi to Claude as a connector or to ChatGPT from its plugin directory, no install required.
Wevi as a connector
Besides the local @wevi/mcp package, Wevi runs a hosted MCP server at:
https://mcp.wevi.ai/mcpClients 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
Wevi is in ChatGPT's plugin directory, so there is nothing to paste.
- Open Wevi in ChatGPT, or open Plugins in ChatGPT's sidebar and search for Wevi.
- Click Try in chat. The first time, ChatGPT asks you to connect: sign in to Wevi and click Allow.
- Start your message with Wevi, for example "Wevi, make a 30-second launch video for my product from its website".
On a Business or Enterprise workspace, an admin may need to allow Wevi first. Where plugins are turned off, Developer mode still works: add a connector with the URL https://mcp.wevi.ai/mcp and choose OAuth.
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.
What the connection can do
The consent page lists the main things: browse your published templates, create projects and render videos, spend your credits, and read render status. The connection can also draft storyboards, open pages in Wevi's own browser (signed in where you signed in yourself, see Capturing private dashboards), capture them into scenes, and change a video's sound design. 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 credit spend appear there like any other key. You can give it a monthly credit cap there; past it, tools answer with
KEY_MONTHLY_CAPuntil the cap is raised or the month turns. - Revoke it to disconnect. The app loses access immediately and has to be reconnected.
- Connectors always run as live keys and spend credits from the same balance as the studio. Buy credits under Profile → Billing. 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.