VULK MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VULK_API_KEY | Yes | Your VULK API key (vk_sk_...) | |
| VULK_API_BASE | No | API base URL | https://vulk.dev |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_visual_briefA | Turn a raw idea into a concise production brief for an immersive VULK project. This does not create a project or call external services. |
| create_projectA | Create a complete VULK project from a prompt and return project, preview, and editor URLs. This may consume account credits. |
| generate_immersive_siteA | Generate a 3D, motion-rich, cinematic VULK web experience from a prompt, visual reference, URL, Figma, screenshot, video reference, or moodboard. Returns delivery URLs, not raw media assets. |
| edit_projectA | Apply a natural-language change to an existing VULK project. VULK updates relevant files and returns preview/editor URLs. |
| list_projectsB | List VULK projects visible to the authenticated account. |
| get_projectA | Get metadata, preview URL, and editor URL for one VULK project. |
| get_project_filesA | Return a project's file manifest. File content is omitted by default and, when requested, is redacted and size-limited. |
| deploy_projectA | Deploy a VULK project to production and return the production URL. Requires an eligible VULK plan. |
| list_modelsA | List AI models available to the authenticated VULK account. |
| get_usageA | Check API usage, credits, and rate-limit status for the authenticated VULK account. |
| subscribeA | Return a VULK pricing or checkout URL. This does not change billing by itself. |
| generateA | Legacy alias for create_project. Prefer create_project or generate_immersive_site in new clients. |
| editC | Legacy alias for edit_project. |
| listB | Legacy alias for list_projects. |
| getB | Legacy alias for get_project. |
| filesA | Legacy alias for get_project_files. Content is omitted by default for safety. |
| deployC | Legacy alias for deploy_project. |
| modelsA | Legacy alias for list_models. |
| usageA | Legacy alias for get_usage. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 19 tools
Many legacy aliases (e.g., deploy, edit, generate) duplicate primary tools, creating confusion about which to use. Tools like create_project and generate_immersive_site have overlapping purposes, and agents may struggle to choose correctly.
Primary tools use snake_case (create_project, deploy_project), but legacy aliases are single words (deploy, edit, list). This inconsistent naming pattern (camelCase is absent, but mixing verb forms and lengths) reduces predictability.
With 19 tools, many are redundant aliases. The core set of about 11 unique tools is reasonable for project creation and deployment, but the extra aliases make the count feel bloated for the actual scope.
CRUD-like operations are partially covered: create, read, update (via edit), list. However, delete is missing, and there is no direct tool to update project metadata (only file edits). Billing is limited to a pricing URL. Notable gaps exist.