Labsco
MCP SERVER

VULK MCP Server

by VULK-dev ↗

Describe a site in chat and VULK builds it — every call answers with preview, editor and production URLs rather than files you have to assemble.

CMS & Blog Publishing✓ Verified
Summary
Prompt to deployed site without leaving the conversation.

create_visual_brief creates nothing and calls nothing, so the shape of the project can be argued out before create_project or generate_immersive_site spends credits — and since both answer with URLs rather than assets, review happens in VULK's own editor. Two things to settle before wiring it up: deploy_project needs an eligible plan, and the legacy aliases are on by default, so the tool list arrives with every capability listed twice until you set VULK_ENABLE_LEGACY_TOOLS=false.

What it is

Chat access to VULK, a prompt-to-site generation service for 3D/WebGL, cinematic and moodboard-driven web projects. The tools create, edit, inspect and deploy projects on the account you authenticate as, and hand back URLs instead of raw media.

What you get
  • A production brief drafted from a raw idea, a URL, a Figma file, a screenshot, a video reference or a moodboard — create_visual_brief is read-only and calls no external service
  • Whole projects generated from a prompt, either general or on the immersive route, returning project, preview and editor URLs
  • Natural-language edits applied to an existing project, with VULK updating the files and answering with fresh preview and editor URLs
  • A project's file manifest, content omitted unless you ask for it — and when you do, .env files, private keys, credentials, service-account files and certificates come back redacted
  • Deployment to production for projects on an eligible plan, returning the production URL
  • The models available to the account, plus credits, usage and rate-limit status
  • A pricing or checkout URL from subscribe, which changes no billing by itself
Requirements

A VULK API key in VULK_API_KEY, taken from vulk.dev/settings/api-keys; keys start with vk_sk_. The local package runs over stdio as npx -y vulk-mcp-server. The remote endpoint at https://mcp.vulk.dev/mcp carries the same tools over Streamable HTTP and authorizes with OAuth 2.0 and PKCE, so there is no key to place. Legacy aliases (generate, edit, list, get, files, deploy, models, usage) ship enabled — VULK_ENABLE_LEGACY_TOOLS=false hides them. File content is capped at 50 KB by default and 200 KB at most; VULK_API_BASE points the client at another base URL. MIT.

Setup effort

One command plus a key — npx -y vulk-mcp-server, then supply credentials