Servers and MCP key

A server groups your sources, tools, target API and an MCP key. This page explains how to manage it.

Create a server

On "My servers", click "Create a server". The name is 1 to 60 characters long with no control characters; the optional description is 500 characters at most. The number of servers is set by your plan (see the "Plans" screen): delete a server to create another one beyond it. Your email address must be verified.

On creation, the MCP key is shown once (see The MCP key).

Server statuses

A server moves from draft to active by itself on the first successful import. A draft or disabled server answers the AI with a 403 error "Server is not active". The sandbox works whatever the status.

Rename a server

In the server detail, click "Edit", change the name or description, then "Save". The key and the URL do not change.

Enable or disable

Use the "Server enabled" switch in the server detail. While disabled, the server refuses AI calls and loses nothing: sources, tools and key are kept. Turn it back on whenever you want.

Delete a server

Click "Delete", then type the server name to confirm. Sources, documents, call log and key are permanently deleted. This cannot be undone.

The MCP key

The key starts with vz_ (for example vz_AbC…). It is a secret: anyone who holds it can call your server. It is shown only once, on creation or regeneration, and Voozeo only keeps a fingerprint of it, so it cannot be retrieved later. Store it in a password manager and never post it in a code repository or a message.

Regenerate the key

If the key is lost or compromised, open the "Connection" tab, click "Regenerate key" and confirm. The old key stops working immediately: reconfigure every connected AI with the new one. A missing, invalid or other-server key causes a 401 error (see Errors and troubleshooting). A server whose target API uses OAuth 2.0 has no key to regenerate: each AI signs in instead (see Servers using OAuth). If you switch such a server back to another authentication type, regenerate the key before connecting an AI.

The two URL forms

The "Connection" tab offers two URLs for the same server. The exact address is the one displayed there.

URL with the key in the header

It ends with /s/<serverId>/mcp and the key is sent in the Authorization: Bearer <key> header. Prefer this form when the client lets you set a header, for example Claude Code, Cursor or VS Code.

URL with the key embedded

It ends with /k/<key>/mcp: the key is part of the address. Use it for clients that only accept a URL, such as claude.ai, Claude Desktop or ChatGPT. Keep this URL secret: it grants access to the server just like the key does. See Connecting your AI.

The "Dashboard" tab summarizes how the server is used: see Dashboard.

Example

You create the server shop, copy the vz_… key into your password manager, then import a spec. The server becomes active. Later, a colleague leaves the team: you click "Regenerate key" and update Claude Code with the new key. The old one no longer works.