Vinkius Deploy

What it does

When your agent uses it

• Configuring remote settings
• Preparing an entrypoint for edge deployment
• Troubleshooting deploy-related errors
• Publish to edge

Example prompts

• “deploy”
• “publish to edge”
• “mcpfusion deploy”
• “/vinkius-deploy”

Requirements

• Node.js
• A credential in MCPFUSION_DEPLOY_TOKEN
• Compatibility (from SKILL.md): Requires Node.js >= 18, MCP Fusion CLI (included in @mcpfusion/core)

Workflow steps

8 steps, taken from the first numbered list in SKILL.md.

1. 1src/server.ts
2. 2src/index.ts
3. 3src/server.js
4. 4src/index.js
5. 5server.ts
6. 6index.ts
7. 7server.js
8. 8index.js

What it can do on your machine

Read from SKILL.md and the folder at commit 1dab501. It shows what the files ask for, not the result of running them.

• Tool permissions

  Pre-approves nothing: there is no allowed-tools line, so your agent's usual permission prompts apply.

  From allowed-tools in the SKILL.md frontmatter.

• Runs code

  Ships script files (TypeScript), which the agent can run.

  Shell commands in SKILL.md call:

  • bundle

  From the folder's file list and the shell code blocks in SKILL.md.

• Network

  Hosts in commands or code, which the agent is likely to contact:

  • cloud.vinkius.com
  • custom.api.com

  From URLs in SKILL.md, links to its own repository left out.

• Credentials

  Names these keys or tokens, usually read from environment variables:

  • MCPFUSION_DEPLOY_TOKEN

  From names ending in _API_KEY, _TOKEN, _SECRET, _KEY or _PASSWORD in SKILL.md.

• Compatibility

  Requires Node.js >= 18, MCP Fusion CLI (included in @mcpfusion/core)

  From compatibility in the SKILL.md frontmatter.

Context cost

Vinkius Deploy loads about 1.7k tokens when it runs, and up to ~3.6k if it reads all its reference files. Until then it costs about 102 tokens; SKILL.md has 446 words of instructions outside code blocks.

Always · name and description, kept in context so the agent knows when to use it

~102

When it runs · the whole SKILL.md, loaded when a task matches

~1.7k

With references · SKILL.md plus every file in references/, read only if the agent opens them

~3.6k

Estimates: characters ÷ 4, the usual rule of thumb; real counts depend on the model's tokenizer. Scripts and assets cost tokens only if the agent reads them.

Safety

• NoteMentions a .env fileSKILL.md:28

  # 2. Set the deploy token in .env

• NoteMentions a .env fileSKILL.md:29

  EN=<connection-token-from-dashboard>" >> .env

• NoteMentions a .env fileSKILL.md:52

  ### `.env` (deploy token)

• NoteMentions a .env fileSKILL.md:110

  read .MCPFusionrc + .env

• NoteMentions a .env fileSKILL.md:204

  | `set MCPFUSION_DEPLOY_TOKEN=<token> in .env` | Token not found | Add token to `.env` or pass `--token` |

Automated static check — not a guarantee. Review scripts before installing. It scans the text of SKILL.md for risky patterns (piping downloads into a shell, reading credential files, hidden Unicode, destructive commands); files beside SKILL.md are not scanned.

SKILL.md

The full file from vinkius-labs/mcpfusion at commit 1dab501, republished under its Apache-2.0 licence (© vinkius-labs). 446 words, ~1,748 tokens.

name

vinkius-deploy

description

How to deploy MCP servers to Vinkius Edge using `mcpfusion deploy`. Use this skill whenever deploying, configuring remote settings, preparing an entrypoint for edge deployment, or troubleshooting deploy-related errors. Activate when the user says "deploy", "publish to edge", "mcpfusion deploy", "push to Vinkius", mentions .MCPFusionrc, MCPFUSION_DEPLOY_TOKEN, or any edge deployment topic.

compatibility

Requires Node.js >= 18, MCP Fusion CLI (included in @mcpfusion/core)

license

Apache-2.0

metadata.author

vinkius-labs

metadata.version

1.0

metadata.tags

deploy, edge, cloud, cli

# 1. Configure the remote (once per project)
MCP mcpfusion remote --server-id <uuid-from-dashboard>

# 2. Set the deploy token in .env
echo "MCPFusion_DEPLOY_TOKEN=<connection-token-from-dashboard>" >> .env

# 3. Deploy
mcpfusion deploy

{
  "remote": "https://cloud.vinkius.com",
  "serverId": "abc-123-def"
}

MCPFUSION_DEPLOY_TOKEN=your-connection-token-here

// WRONG — autoDiscover() scans the filesystem at runtime
await autoDiscover(registry, fileURLToPath(new URL('./tools', import.meta.url)));

// CORRECT — explicit imports for edge
import { listUsers } from './tools/users.js';
import { getInvoice } from './tools/billing.js';
registry.register(listUsers);
registry.register(getInvoice);

- import { autoDiscover } from '@mcpfusion/core';
+ // Explicit imports — no filesystem in V8 isolates
+ import { listProducts } from './tools/product.js';
+ import { getInvoice } from './tools/billing.js';

  const registry = f.registry();
- await autoDiscover(registry, ...);
+ registry.register(listProducts);
+ registry.register(getInvoice);

read .MCPFusionrc + .env
       ↓
resolve entrypoint (src/server.ts → src/index.ts → server.ts → index.ts)
       ↓
check for edge-incompatible APIs (autoDiscover, SandboxEngine, Inspector)
       ↓
esbuild bundle (IIFE, platform: browser, es2022, tree-shaking, minify)
       ↓
size check (max 500KB raw)
       ↓
gzip compress + SHA256 hash
       ↓
POST /servers/:serverId/deploy (Bearer token)
       ↓
response: { deployment_id, server_name, url }

mcpfusion deploy                        # auto-detect entrypoint
mcpfusion deploy --server ./src/app.ts  # explicit entrypoint
mcpfusion deploy --token <token>        # override MCPFUSION_DEPLOY_TOKEN
mcpfusion deploy --allow-insecure       # suppress HTTP plaintext warning

MCP mcpfusion remote                              # show current config
MCP mcpfusion remote --server-id <uuid>           # set server ID (uses default cloud)
MCP mcpfusion remote https://custom.api.com       # override API endpoint
MCP mcpfusion remote https://custom.api.com --server-id <uuid>  # both at once

mcpfusion dev --server ./src/server.ts
mcpfusion dev --server ./src/server.ts --dir ./src/tools

fusion lock                               # generate/update lockfile
fusion lock --check                       # verify (CI gate)

mcpfusion create my-server
mcpfusion create my-server -y                 # skip prompts
mcpfusion create my-server --vector prisma --transport sse

mcpfusion inspect --demo            # built-in simulator
fusion insp --pid 12345          # connect to server PID

© vinkius-labs, Apache-2.0. Rendered from Markdown: HTML in the file is shown as text, images as links, and headings moved down two levels. Raw file

Files

SKILL.md and 1 other file (references) in .claude/skills/vinkius-deploy of vinkius-labs/mcpfusion.

• SKILL.md
• references/example-edge-server.ts

Open the folder on GitHubat commit 1dab501