VSLZ AIWorkspace
OverviewMCP ServerAPI ReferenceChangelog

Install the VSLZ MCP server

Use the local stdio MCP package with Claude Desktop, Claude Code, and Cursor. Each client gets its own install path below.

Local stdio only in this release
This release covers the local stdio MCP package only. You need a VSLZ API key to authenticate. Remote MCP or OAuth setup is not part of this flow.

1. Generate an API key

Create your key in Settings before configuring any client. The full key is shown once — copy it immediately. The published package name is @vslzai/mcp-server.

Open API keys

2. Environment variables

VSLZ_API_KEY is required. VSLZ_BASE_URL is optional and defaults to production.

VariableRequiredDefaultNotes
VSLZ_API_KEYRequiredNoneAPI key created in VSLZ Settings. Sent as bearer auth on every MCP-backed request.
VSLZ_BASE_URLOptionalhttps://vslzai.comOverride the API origin when targeting a non-production deployment.

3. Claude Code

Claude Code is the only client in this release with a one-line claude mcp add install. This section is for Claude Code CLI only.

Claude Code install command
claude mcp add --transport stdio --env VSLZ_API_KEY=<YOUR_KEY> vslz -- npx -y @vslzai/mcp-server
Verification
  • -Run `claude mcp list` and confirm `vslz` appears as a stdio server.
  • -Start a Claude Code session and confirm the VSLZ tools are available.
  • -Call `vslz_list_sessions` and verify it returns your account sessions.

4. General MCP client

For Claude Desktop, Cursor, Windsurf, Codex, or any other MCP-compatible client, add this JSON to your client's MCP config file. Replace the API key value with your own.

MCP config JSON
{
  "mcpServers": {
    "vslz": {
      "command": "npx",
      "args": ["-y", "@vslzai/mcp-server"],
      "env": {
        "VSLZ_API_KEY": "vslz_your_key_here"
      }
    }
  }
}
Verification
  • -Restart or reload your client after saving the config.
  • -Open the tools panel and confirm VSLZ tools are listed.
  • -Run vslz_list_sessions to verify the server can reach your account.

5. Available tools

vslz_analyze

Start an async analysis run, poll it to completion, and return the summarized result.

vslz_upload

Upload a local file into a VSLZ session or the global file library.

vslz_list_files

List session-scoped files and global files available to the authenticated account.

vslz_get_schema

Fetch the schema card associated with a session or global file.

vslz_query

Run a synchronous query and return the completed result in one response.

vslz_export

Return chart JSON or download a generated output file to disk.

vslz_list_sessions

List sessions for the authenticated VSLZ account.

6. Quick verification workflow

  1. Run vslz_list_sessions to confirm the client can authenticate and reach your account.
  2. Upload a CSV with vslz_upload into a session or the global library.
  3. Inspect the uploaded file with vslz_get_schema.
  4. Run vslz_analyze with a chart or analysis request.
  5. Export the resulting output with vslz_export.