VULK

io.github.VULK-devv1.2.0Updated Oct 9, 2026

Create and continue apps and websites with your own VULK plan and credits.

VerifiedStreamable HTTPWeb executableDeveloper ToolsProductivity & Workflow

Overview

AI-generated overview

Lets an assistant work with your own VULK account to list projects, read plan and credit usage, and start or continue app and website builds.

What it does
The connector exposes tools to list your projects, read a project's details and links, and on paid plans read its source files. It reports your plan, renewal date, credit balance and 30-day usage, and can start a new project from a written brief or send the next instruction to an existing one, then read the build's progress, questions and editor link. It can also stop a running build. Publishing, buying credits, changing plans and deleting projects are not available.
When to use it
Use it when you want an assistant to drive VULK builds from a written brief inside your own account, or to check project status, plan and credit usage without opening the VULK editor. It is not for standalone image, video or audio generation.
Requirements
A remote Streamable HTTP endpoint; no local package or API key. You need a VULK account and must sign in and approve the connection through OAuth 2.0 with PKCE and dynamic client registration. Reading and building are separate permissions, so projects.write must be granted for build tools. Network access to the VULK endpoint is required.
Before you install
The connection acts inside your signed-in VULK account and can create projects and send build instructions, which consumes the credits your plan includes; if no credits remain, requests are refused. The brief text you give the assistant is sent to VULK, up to 8,000 characters. A connection lasts up to 90 days and can be revoked in Settings. The older npm packages vulk-mcp-server and @vulk/mcp-server are separate and use VULK_API_KEY instead of OAuth.

Installation

In SourceWeft

  1. Open VULK in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "vulk-mcp-server": {
      "type": "http",
      "url": "https://app.vulk.dev/mcp"
    }
  }
}

README

VULK MCP connector

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.

What an assistant can do

  • List your projects, read a project's details and, on a paid plan, its source files.
  • Show your plan and renewal date, your credit balance and your usage over the last 30 days.
  • Create a new project, or send the next instruction to an existing one. VULK builds it the way it does in its own editor, using the credits your plan already includes. The assistant can then read the progress, any questions VULK asks, and the link that opens the result in the editor.
  • Stop a request that is still running.

What it cannot do

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.

Connect

  • Claude (claude.ai): Customize › Connectors › Add custom connector, name VULK, URL https://app.vulk.dev/mcp.

  • Claude Code:

    bash
    claude mcp add --transport http vulk https://app.vulk.dev/mcp

  • Codex CLI:

    bash
    codex mcp add vulk --url https://app.vulk.dev/mcpcodex mcp login vulk

  • Cursor: add to mcp.json:

    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.

Tools

ToolScopeWhat it does
list_projectsprojects.readYour projects
get_projectprojects.readOne project's details and links
get_project_filesprojects.readThe file index, or one source file per call (paid plans)
get_usageusage.readPlan, renewal date, credit balance, 30-day usage
open_billingnoneReturns a link to your own billing page; changes nothing
create_projectprojects.writeStarts a build of a new project from your brief
continue_projectprojects.writeSends the next instruction or answer to an existing project
get_operationprojects.readReads the persisted state of a build you started
stop_operationprojects.writeAsks 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.

Permissions, data and revocation

  • A connection lasts up to 90 days (refresh tokens rotate on every use) and you can remove it at any time in Settings › Integrations › Connected apps at app.vulk.dev.
  • The connector reads and writes only inside the signed-in account: its projects, plan, credits and usage. The text you ask the assistant to build is sent to VULK as the project brief (up to 8,000 characters).
  • Each build request carries a request_id; repeating a request with the same id returns the same receipt instead of building twice.

Legacy local package

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.

License

MIT. See LICENSE.

Source: README.md at commit 8b8c7fd

Tools

0
Tool metadata has not been indexed yet.

Version history

1
  1. v1.2.0LatestOct 9, 2026