Veryfront Code

Development MCP server built into the Veryfront CLI, for coding agents working on a Veryfront app

Official · Veryfront TypeScript Local · stdio, Streamable HTTP Developer toolsCloud platforms

57 popularity score ★ 20 ↓ 9.1k/wk

Connect your client

Local (once it is running)

Add in one click

Opens the app, which asks before it adds the server.

Or add it by command or config

Claude CodeTerminal
claude mcp add --transport http veryfront-code http://localhost:3002/mcp
Cursor~/.cursor/mcp.json
{
  "mcpServers": {
    "veryfront-code": {
      "url": "http://localhost:3002/mcp"
    }
  }
}
VS Code.vscode/mcp.json
{
  "servers": {
    "veryfront-code": {
      "type": "http",
      "url": "http://localhost:3002/mcp"
    }
  }
}
Codex~/.codex/config.toml
[mcp_servers.veryfront-code]
url = "http://localhost:3002/mcp"
Gemini CLITerminal
gemini mcp add --scope user --transport http veryfront-code http://localhost:3002/mcp
Local (npm)

Add in one click

Opens the app, which asks before it adds the server.

Or add it by command or config

FirstTerminal
npm install -g veryfront
Claude CodeTerminal
claude mcp add veryfront-code -- veryfront mcp
Claude Desktopclaude_desktop_config.json
{
  "mcpServers": {
    "veryfront-code": {
      "command": "veryfront",
      "args": [
        "mcp"
      ]
    }
  }
}
Cursor~/.cursor/mcp.json
{
  "mcpServers": {
    "veryfront-code": {
      "command": "veryfront",
      "args": [
        "mcp"
      ]
    }
  }
}
VS Code.vscode/mcp.json
{
  "servers": {
    "veryfront-code": {
      "type": "stdio",
      "command": "veryfront",
      "args": [
        "mcp"
      ]
    }
  }
}
Codex~/.codex/config.toml
[mcp_servers.veryfront-code]
command = "veryfront"
args = ["mcp"]
Gemini CLITerminal
gemini mcp add --scope user veryfront-code veryfront -- mcp

Settings 3

VERYFRONT_API_TOKEN Optional: Veryfront account token for vf_trigger_deploy and the vf_remote_* tools; a token stored by `veryfront login` also works.
CONTEXT7_API_KEY Optional: Enables the c7_resolve_library and c7_query_docs documentation tools.
VERYFRONT_API_BASE_URL Optional: API address for the remote file tools; https://api.veryfront.com by default.

What it does

Veryfront Code is an open-source TypeScript and React framework for building AI apps and agents. Its `veryfront` CLI carries an MCP server of its own, meant for coding agents (Claude Code, Cursor, Codex and others) that edit a Veryfront project. This page covers that dev-time server, not the framework's separate feature for exposing your own app's tools over MCP.

The server runs two ways. While `veryfront dev` is running, an HTTP endpoint listens at http://localhost:3002/mcp (two ports above the port the dev server bound, path always /mcp). Separately, `veryfront mcp` starts a stdio server for clients that can only launch a command; it fetches live data from the running dev server over HTTP and reports that the dev server is not running when it cannot reach it.

Through it an agent can read compile, runtime, bundle and HMR errors and dev-server logs, list and preview routes, scaffold routes, components and AI primitives, run the project's tests and linter, force a browser refresh, start new projects from templates, and trigger a deploy to Veryfront's cloud. The HTTP endpoint also offers file and branch tools for remote projects on Veryfront's hosted platform, markdown issue files kept in the project, and Context7 documentation lookups.

The two ways do not expose the same tools. In version 0.1.1273 the HTTP endpoint registers 51 tools (cli/mcp/tools.ts and advanced-tools.ts), while the stdio server started by `veryfront mcp` defines its own shorter list of 13 (cli/mcp/standalone.ts). The remote file, branch, issue and catalog tools are on the HTTP endpoint only.

What it needs

RuntimeNode.js 22+

Node.js 22.3.0 or later (the package's engines field), with the `veryfront` CLI installed (npm install -g veryfront), and a Veryfront project to work in. Most tools need `veryfront dev` running in that project. Deploys and the remote-project tools need a Veryfront account token (VERYFRONT_API_TOKEN or `veryfront login`); the c7_* tools need a CONTEXT7_API_KEY.

Limits

Development use only: `veryfront start` does not expose the vf_* tools in production. The stdio command offers 13 of the 51 tools; the remote file, branch, issues and project-catalog tools exist only on the HTTP endpoint that `veryfront dev` opens. The HTTP endpoint accepts requests only from localhost, 127.0.0.1 and [::1] origins, so browser-based agents on other origins are refused. If the requested dev port is taken the dev server moves to the next free one and the MCP port moves with it, so the client URL has to follow the port the dev server prints. Without CONTEXT7_API_KEY the c7_* tools return a not-configured error.

Who it suits

Suits developers building on the Veryfront framework who want their coding agent to see live errors, routes and test results instead of guessing. Pick the HTTP endpoint when your client takes a remote URL (it has the full tool set), and `veryfront mcp` only for stdio-only clients. It is of no use outside a Veryfront project: it works on that framework's dev server, not general web apps. Leave the deploy and remote-project tools unconfigured (no token) if you want the agent to stay local.

Tools 34 of 51

vf_get_errors
Return live compile, runtime, bundle, HMR and module errors, filtered by type or file; 50 by default
vf_get_logs
Return dev-server log entries filtered by level, source or text; 100 by default
vf_get_status
Show dev-server uptime, ports and active features
vf_clear_errors
Empty the collected error list
vf_clear_cache
Delete the framework's module and MDX caches
vf_list_routes
List the routes the dev server has registered
vf_preview_route
Fetch a route's HTTP response without a browser
vf_scaffold
Generate routes, components, agents, tools and other project files
vf_get_conventions
Explain the project's file conventions before new files are added
vf_run_tests
Run the project's test suite
vf_run_lint
Run the project's linter
vf_trigger_hmr
Force a browser refresh after a file changed outside the dev server
vf_bootstrap
Give the agent its starting context for a session
vf_get_schema
Return the CLI's command schema
vf_get_project_info
Report project and runtime configuration
vf_list_templates
List the templates new projects can start from
vf_list_integrations
List the available integration connectors
vf_create_project
Create a new local project from a template
vf_list_local_projects
Find Veryfront projects on the local disk
vf_trigger_deploy
Release a branch and deploy it to an environment on Veryfront's cloud
vf_remote_list_files
List files in a hosted Veryfront project
vf_remote_get_file
Read a file from a hosted project
vf_remote_update_file
Write a file in a hosted project
vf_remote_delete_file
Delete a file in a hosted project
vf_remote_search_files
Search file contents in a hosted project
vf_remote_move_file
Move or rename a file in a hosted project
vf_remote_list_branches
List branches of a hosted project
vf_remote_create_branch
Create a branch in a hosted project
vf_remote_merge_branch
Merge a branch, into main unless another target is given
vf_remote_delete_branch
Delete a branch of a hosted project
vf_remote_create_project
Create a project on Veryfront's hosted platform
vf_remote_clone_project
Copy a hosted project
c7_resolve_library
Find a library's Context7 id (needs CONTEXT7_API_KEY)
c7_query_docs
Fetch library documentation from Context7 (needs CONTEXT7_API_KEY)

Similar servers