Skip to main content
The Versuno MCP server is distributed on npm as versuno-mcp. You don’t install it manually. Your MCP client launches it on demand via npx.

​
Requirements

​
The universal config

Every MCP client uses some variation of the same config block: 
{
  "command": "npx",
  "args": ["-y", "versuno-mcp"],
  "env": {
    "VERSUNO_API_KEY": "uk_live_xxx"
  }
}
The -y flag tells npx to auto-install without prompting. Subsequent runs use the cached binary. Client-specific instructions:

​
Environment variables

VariableRequiredDescription
VERSUNO_API_KEYYesYour Versuno API key. Must start with uk_live_.
VERSUNO_API_URLNoOverride the API base URL. Defaults to https://versuno.ai/api/public. Useful for self-hosted Versuno or staging environments.
VERSUNO_DEBUGNoSet to 1 to log HTTP requests to stderr. Useful for troubleshooting connection issues.

​
Verifying it works

After configuring your client, restart it and open a chat. The agent should have access to five new tools:
  • list_assets
  • search_assets
  • get_asset
  • pull_asset
  • push_asset
Ask the agent: “List my Versuno assets.” It should call list_assets and return metadata for up to 20 assets. If it doesn’t, the server isn’t connected. See Troubleshooting.

​
Troubleshooting

The agent doesn’t see any Versuno tools. The server isn’t being launched. Check:
  1. The MCP client’s config file is saved and the client has been fully restarted.
  2. npx is on your PATH. Run npx --version from your terminal.
  3. Node.js 18 or newer is installed. Run node --version.
VERSUNO_API_KEY is not set. The env block isn’t reaching the spawned process. Double-check the JSON structure. Some clients need env inside the server block, not at the top level. VERSUNO_API_KEY is invalid. Your key doesn’t start with uk_live_ or is too short. Regenerate it at versuno.ai/settings/api-keys. AUTH_FAILED on every tool call. The key was revoked or copied incorrectly. Regenerate and update the config. Intermittent timeouts. Set VERSUNO_DEBUG=1 in the env block, restart the client, and check its MCP log panel for the actual HTTP errors.

​
Installing a specific version

npx -y versuno-mcp always pulls the latest release. To pin a version, add it to the package spec: 
{
  "command": "npx",
  "args": ["-y", "versuno-mcp@0.1.0"],
  "env": {
    "VERSUNO_API_KEY": "uk_live_xxx"
  }
}
See the changelog for release notes.