
Connects Claude and other MCP clients to VULK's 3D/WebGL project generation API. You get tools to create immersive sites from natural language briefs, edit existing projects, inspect file manifests, and deploy to production. Supports both local stdio with API key auth and remote HTTPS transport with OAuth 2.0/PKCE. File operations default to manifests only and redact credentials automatically. Good fit if you're building workflows that go from prompt to live 3D site without leaving the chat interface. The remote connector at mcp.vulk.dev/mcp handles OAuth discovery and token refresh, while the local package runs via npx with your VULK_API_KEY.
VULK builds apps and websites from a written brief. This connector lets an AI assistant work with your own VULK account once you have signed in and approved it.
https://app.vulk.dev/mcp (alias https://mcp.vulk.dev/mcp)It cannot publish a site, buy credits, change your plan or delete a project: there is no tool for any of those. If your plan has no credits left, VULK refuses the request. There is no standalone image, video or audio generation tool; media is only ever generated as part of building a project, as one of its design assets.
Claude (claude.ai): Customize › Connectors › Add custom connector, name VULK, URL https://app.vulk.dev/mcp.
Claude Code:
claude mcp add --transport http vulk https://app.vulk.dev/mcp
Codex CLI:
codex mcp add vulk --url https://app.vulk.dev/mcp
codex mcp login vulk
Cursor: add to mcp.json:
{ "mcpServers": { "vulk": { "url": "https://app.vulk.dev/mcp" } } }
Any other MCP client that supports remote servers with OAuth: add the URL above.
The first time, you are sent to app.vulk.dev to sign in and see what the connection can do before you approve it.
| Tool | Scope | What it does |
|---|---|---|
list_projects | projects.read | Your projects |
get_project | projects.read | One project's details and links |
get_project_files | projects.read | The file index, or one source file per call (paid plans) |
get_usage | usage.read | Plan, renewal date, credit balance, 30-day usage |
open_billing | none | Returns a link to your own billing page; changes nothing |
create_project | projects.write | Starts a build of a new project from your brief |
continue_project | projects.write | Sends the next instruction or answer to an existing project |
get_operation | projects.read | Reads the persisted state of a build you started |
stop_operation | projects.write | Asks VULK to stop a build that is still running |
Reading and building are separate permissions: a connection that was not granted projects.write never sees the tools that need it, and a call to one anyway returns a tool error that names the missing permission.
request_id; repeating a request with the same id returns the same receipt instead of building twice.The npm packages vulk-mcp-server (1.1.0 and earlier) and @vulk/mcp-server (1.0.0) are separate local command-line packages (they run on your own machine) from before this connector. They authenticate with an API key (VULK_API_KEY) instead of OAuth and expose different tools. This connector does not use them, and their tool names and behaviour are not described here.
MIT. See LICENSE.
VULK_API_KEY*secretYour VULK API key (get at vulk.dev/settings/api-keys)