MCP server

Overview

• Server address: https://qevio.ai/api/mcp
• Transport: Streamable HTTP (MCP's remote transport), stateless, JSON responses. No local install needed.
• Sign-in: sign in with your Qevio account (OAuth) in apps that support it, such as claude.ai and ChatGPT, or use a personal key in apps that take one. See Authentication.
• Billing: generations use your Qevio credits, at the same prices as on the site. Outputs that fail are refunded automatically.

Setup

claude.ai, Claude Desktop and ChatGPT: sign in

These apps sign in to Qevio for you, so you don't need a key.

1. Add a custom connector. In Claude, that's Settings → Connectors → Add custom connector. In ChatGPT, it's under Settings → Connectors (some plans need developer mode turned on first). Menu names change from time to time.
2. Enter the name Qevio and the server address https://qevio.ai/api/mcp. Leave any client ID and secret fields empty.
3. Click Connect. Qevio opens: log in if asked, check the app's name and where it sends you back, and click Allow.

Apps that take a key

Claude Code, Cursor, Windsurf, VS Code and most other MCP apps can also send a personal key with each request.

1. Make a key. Log in and open Settings → Connect AI apps. Name the key after the app you'll use it in and click Make key. Copy it straight away: it's shown only once. The same card shows these setup lines with your key already filled in.

2. Add Qevio to your AI app. Replace YOUR_KEY with your key.

Claude Code

Run in a terminal:

claude mcp add --transport http qevio https://qevio.ai/api/mcp --header "Authorization: Bearer YOUR_KEY"

Cursor, Windsurf and other apps

Add this to the app's MCP settings file (in Cursor, ~/.cursor/mcp.json):

{
  "mcpServers": {
    "qevio": {
      "url": "https://qevio.ai/api/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_KEY"
      }
    }
  }
}

VS Code

Add this to .vscode/mcp.json in your project, or to your user MCP settings:

{
  "servers": {
    "qevio": {
      "type": "http",
      "url": "https://qevio.ai/api/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_KEY"
      }
    }
  }
}

3. Try it. Ask your AI app: “What's my Qevio credit balance?”

Authentication

Every request needs an Authorization: Bearer … header with either a sign-in token or a personal key. Without one, the server answers HTTP 401 and points the app to its sign-in details.

Sign-in (OAuth)

• Standard OAuth 2.1 with PKCE (S256), as MCP apps expect. Apps register themselves automatically (dynamic client registration) and find everything from /.well-known/oauth-protected-resource and /.well-known/oauth-authorization-server.
• Nothing happens until you click Allow on Qevio's own page, signed in to your account. The page shows the app's name (as the app describes itself) and the site it returns you to.
• Access tokens last an hour; the app renews them by itself. Each renewal replaces the old tokens.
• Signed-in apps are listed in Settings → Connect AI apps. Disconnect ends an app's access straight away. Suspending an account ends it too.

Personal keys

• Keys start with qv_ and are sent as Authorization: Bearer qv_….
• A key acts as your account and can spend your credits. Keep it private, and never put it in a public repository or a website.
• You can have up to 10 keys. Settings shows each key's name, its first characters, when it was made and when it was last used.
• Revoke a key in Settings at any time. Apps using it lose access on their next request.
• Qevio stores only a fingerprint (hash) of each key, so a key can't be shown again or recovered. Make a new one instead.
• Keys stop working if the account is suspended.

Tools

Arguments for quote and generate

Results from get_generation have a status of queued, running, completed or failed, plus a viewUrl to see them on Qevio. Written content usually takes seconds; videos usually take a few minutes.

Usage examples

Ask in plain words

• “How many Qevio credits do I have?”
• “How much would a 10-second vertical video ad for my coffee brand cost on Qevio?”
• “Make it, and tell me when it's ready.”
• “Write five TikTok captions and hashtags for our summer sale with Qevio, using my Brand Kit.”
• “Show my last five Qevio generations.”

A well-behaved app calls quote first, tells you the price, then calls generate with that price as max_credits, and checks get_generation until the result is done.

Raw requests (for developers)

List the tools:

curl -s https://qevio.ai/api/mcp \
  -H "Authorization: Bearer YOUR_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

Price two written outputs without charging anything:

curl -s https://qevio.ai/api/mcp \
  -H "Authorization: Bearer YOUR_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"quote","arguments":{"kind":"copy","prompt":"Cold brew coffee in a can","outputs":["titles","caption"]}}}'

Credits and limits

• Prices are worked out on Qevio's server, exactly as in Studio. generate never charges more than max_credits.
• Credits are held when a generation starts. Only outputs that succeed are kept; failed ones are refunded automatically.
• Up to 60 requests a minute per account, up to 10 new generations a minute (shared with Studio), and up to 3 generations running at once.
• While Qevio is in maintenance mode, tools are paused for everyone except admins.

Troubleshooting

Still stuck? Email support@qevio.ai with the app you use and the exact error, but never your key.

Not available yet

• Generations through MCP start from a prompt. Attaching photos or files, camera presets and image looks, AI influencers and the video editing tools are only on the website for now.
• Sign-in grants every tool; there are no narrower permissions (such as read-only) yet.