VS Code
Add a .vscode/mcp.json file to your project. VS Code asks for the API key the first time and stores it securely:
{ "inputs": [ { "type": "promptString", "id": "vaif-api-key", "description": "VAIF Studio API key", "password": true } ], "servers": { "vaif-studio": { "type": "stdio", "command": "npx", "args": [ "-y", "@vaifstudio/mcp" ], "env": { "VAIF_PROJECT_ID": "your-project-id", "VAIF_API_KEY": "${input:vaif-api-key}" } } }}Or add it for your user from a terminal:
code --add-mcp '{"name":"vaif-studio","command":"npx","args":["-y","@vaifstudio/mcp"],"env":{"VAIF_PROJECT_ID":"your-project-id"}}'The tools appear in the Chat view when it is in agent mode.
Settings
Section titled “Settings”| Variable | Needed for | Where it comes from |
|---|---|---|
VAIF_PROJECT_ID |
Everything | Your project ID, from the console or vaif.config.json |
VAIF_API_KEY |
The row tools (query_rows, insert_row and the rest) and signed file links |
A project API key, from the project’s Overview or Project settings > API keys. get_signed_url needs a key with the storage scope |
VAIF_AUTH_TOKEN |
Schema, SQL, storage, functions and key tools | Optional. Without it, the server uses the sign-in that vaif login saved in ~/.vaif/auth.json, read again on every call |
VAIF_API_URL |
A local or self-hosted API only | Defaults to https://api.vaif.studio |
Keep API keys out of files you commit.
See MCP server for the tools and what each one can change.