
VULK
io.github.devjoaocastroPublished by GitHub account devjoaocastrov1.1.1Updated Nov 2, 2026
Generate, edit, and deploy immersive 3D/WebGL web projects from any MCP assistant.
Overview
Connects an assistant to a VULK account to list projects, start or continue 3D/WebGL site builds from a brief, and check credits and usage.
- What you can do
- List projects and read a project's details, links and, on paid plans, its source files
- Check plan, renewal date, credit balance and 30-day usage, and get a link to the billing page
- Start a new project build from a written brief, or send the next instruction or answer to an existing one
- Read the persisted state of a running build and stop a build that is still running
- When to use it
- Useful when you want an assistant to turn a written brief into a VULK 3D/WebGL web project, iterate on an existing project, or check remaining credits and usage before starting a build.
- Requirements
- Remote Streamable HTTP endpoint at app.vulk.dev/mcp (alias mcp.vulk.dev/mcp), or the legacy local npm package over stdio. The connector uses OAuth 2.0 with PKCE and dynamic client registration; you sign in to app.vulk.dev and approve the connection. A VULK account and plan credits are needed to build.
Installation
In SourceWeft
- Open VULK in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- 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.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.devjoaocastro%2Fvulk-mcp-server/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"vulk": {
"type": "http",
"url": "https://mcp.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.
- Server URL:
https://app.vulk.dev/mcp(aliashttps://mcp.vulk.dev/mcp) - Transport: remote, Streamable HTTP
- Authentication: OAuth 2.0 authorization code with PKCE (S256), dynamic client registration; no API key
- Documentation: https://support.vulk.dev/docs/api/mcp
- Privacy policy: https://vulk.dev/privacy-policy
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, URLhttps://app.vulk.dev/mcp. -
Claude Code:
-
Codex CLI:
-
Cursor: add to
mcp.json: -
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
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
0Version history
1- v1.1.1LatestSep 16, 2026
Score
85% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts