CLI

Ask AI about Vinkius

Every mcpfusion command explained: scaffold, dev, yaml, inspect, lock, deploy, remote and token, from first scaffold to free hosting on Vinkius Cloud.

The mcpfusion CLI covers the whole life of a connector: scaffold, develop, inspect, lock, deploy. This page is the reference; each command links to the page that explains the concept behind it.

Commands

Command	What it does
`mcpfusion create my-server`	Scaffold a new project, including `SKILL.md` and agent rule files
`mcpfusion dev --server ./src/server.ts`	Run locally with hot reload
`mcpfusion yaml dev`	Run a zero code YAML toolset with `@mcpfusion/yaml`
`mcpfusion inspect`	Real time TUI dashboard for a running server
`mcpfusion lock`	Generate the capability lockfile
`mcpfusion lock --check ./dist/server.js`	CI gate: fail on surface drift
`mcpfusion deploy`	Bundle and host on the Vinkius Edge, free
`mcpfusion remote --server-id <id> --token <token>`	Link a deployed connector to your project
`mcpfusion token <token>`	Store a connection token for client configuration

Scaffold options

bash

npx @mcpfusion/core create my-server \
  --transport stdio \
  --vector prisma \
  --target vercel \
  --testing

Flag	Values	Effect
`--transport`	`stdio`, `http`, `stateless`	How clients talk to the server locally
`--vector`	`vanilla`, `prisma`, `n8n`, `openapi`, `oauth`	Starter integration for the scaffold
`--target`	`vercel`, `cloudflare`	Pre wire the matching adapter, see Self hosting
`--testing` / `--no-testing`	boolean	Include the `@mcpfusion/testing` harness
`--yes`	boolean	Accept every default

Inspect

bash

mcpfusion inspect

inspect attaches to a running server and streams a live dashboard: tools listed, calls arriving, latencies, errors. It uses an out of band channel because the stdio transport belongs to the MCP client and cannot be polluted. It is the fastest way to watch a Presenter's output while a client talks to your server.

Deploy and beyond

bash

mcpfusion deploy
mcpfusion remote --server-id a1b2c3 --token vk_live_…
mcpfusion token vk_live_…

deploy is the free hosting path described in Deploy. remote remembers which deployed connector belongs to this project, so later deploys need no arguments. token keeps the connection token local for client setup.

Put mcpfusion lock --check in CI before mcpfusion deploy. The lockfile proves the surface you tested is the surface you ship. See Governance.

Next steps

Installation: getting the CLI and packages
Deploy: what the deploy actually provisions
Testing: the other CI gate