CodeQL Development MCP Server
OFFICIAL SERVERWrite, test, run and profile CodeQL queries from an AI assistant through the local CodeQL CLI
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
Opens the app, which asks before it adds the server.
claude mcp add --transport http veryfront-code http://localhost:3002/mcp{
"mcpServers": {
"veryfront-code": {
"url": "http://localhost:3002/mcp"
}
}
}{
"servers": {
"veryfront-code": {
"type": "http",
"url": "http://localhost:3002/mcp"
}
}
}[mcp_servers.veryfront-code]
url = "http://localhost:3002/mcp"gemini mcp add --scope user --transport http veryfront-code http://localhost:3002/mcpOpens the app, which asks before it adds the server.
npm install -g veryfrontclaude mcp add veryfront-code -- veryfront mcp{
"mcpServers": {
"veryfront-code": {
"command": "veryfront",
"args": [
"mcp"
]
}
}
}{
"mcpServers": {
"veryfront-code": {
"command": "veryfront",
"args": [
"mcp"
]
}
}
}{
"servers": {
"veryfront-code": {
"type": "stdio",
"command": "veryfront",
"args": [
"mcp"
]
}
}
}[mcp_servers.veryfront-code]
command = "veryfront"
args = ["mcp"]gemini mcp add --scope user veryfront-code veryfront -- mcpVERYFRONT_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. |
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.
| Runtime | Node.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.
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.
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.
vf_get_errorsvf_get_logsvf_get_statusvf_clear_errorsvf_clear_cachevf_list_routesvf_preview_routevf_scaffoldvf_get_conventionsvf_run_testsvf_run_lintvf_trigger_hmrvf_bootstrapvf_get_schemavf_get_project_infovf_list_templatesvf_list_integrationsvf_create_projectvf_list_local_projectsvf_trigger_deployvf_remote_list_filesvf_remote_get_filevf_remote_update_filevf_remote_delete_filevf_remote_search_filesvf_remote_move_filevf_remote_list_branchesvf_remote_create_branchvf_remote_merge_branchvf_remote_delete_branchvf_remote_create_projectvf_remote_clone_projectc7_resolve_libraryc7_query_docs