OVB3 Bridge
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VBCS_APP_NAME | No | Optional single-app default. | |
| VBCS_BASE_URL | No | A standalone VBCS instance's own REST API base URL. | |
| VBCS_REPO_PATH | No | Optional single-repo default, for when a tool call doesn't specify one explicitly. | |
| VBS_WORKSPACE_DIR | No | A local directory containing checkouts of one or more VB Studio project repos. | |
| VBCS_IDCS_PASSWORD | No | Password for standalone VBCS instance REST API. | |
| VBCS_IDCS_USERNAME | No | Username for standalone VBCS instance REST API. | |
| VBSTUDIO_GIT_TOKEN | No | Git remote auth token for commit/push/pull helpers. | |
| VBSTUDIO_API_BASE_URL | No | VB Studio's own REST API base URL (builds, pipelines, issues). Can be left blank; vbstudio_* tools are stubs. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| doctorA | Diagnose this install: Node/git, workspace + repos, git credentials, build tools, Component Exchange URL, and optional services. Reports what's missing and the exact fix; never prints secrets. Run this first when something doesn't work. Set live=true to also test the standalone-VBCS login. |
| list_reposA | List local VB Studio project repo checkouts discoverable under VBS_WORKSPACE_DIR. |
| list_appsB | List VBCS web app names (webApps/) present in a repo checkout. |
| read_artifactB | Read a VBCS artifact file (page/flow/chain/service JSON, etc) by repo-relative path. |
| write_artifactB | Write a VBCS artifact file by repo-relative path. Refuses invalid JSON for .json paths and any path outside the repo. |
| list_artifactsA | List artifact files in a repo matching a glob pattern (file names only), e.g. 'webApps//flows/**/.json'. To search file CONTENT use search_artifacts. |
| search_artifactsA | Search artifact file CONTENT across a repo (grep). Substring by default, or a regex. Defaults to webApps/services/settings .js/.json/.html/.css/.md files; narrow with glob. |
| audit_service_callsA | Cross-app audit of REST service usage: finds every Actions.callRest call in the repo's action-chain JS, and for each service endpoint compares which parameter keys (uriParams/body/headers…) each app passes, flagging keys some apps send that others omit. Compares key sets, not values. Use it to check a shared service connection is mapped consistently across apps. |
| git_statusB | Show git status for a repo checkout. |
| git_commitB | Stage and commit changes in a repo checkout. |
| git_pullB | Pull from the repo's remote. Authenticates with VBSTUDIO_GIT_USERNAME/TOKEN when set; never hangs on a hidden prompt. |
| git_pushB | Push to the repo's remote. Authenticates with VBSTUDIO_GIT_USERNAME/TOKEN when set; never hangs on a hidden prompt. |
| git_cloneA | Clone a git remote into VBS_WORKSPACE_DIR so it's discoverable by list_repos. Used by /link's VBS setup flow. Do not embed credentials in remoteUrl - set VBSTUDIO_GIT_USERNAME/TOKEN instead. |
| setup_build_toolsA | Install a repo's build dependencies ( |
| run_buildA | Run grunt-vb-build for a VBCS app. Streams output live to server logs. Needs setup_build_tools first, and VB_BUILD_COMPONENT_EXCHANGE_URL for apps using web components; failures include a plain-language hint. |
| run_auditA | Run grunt-vb-audit for a VBCS app. Streams output live to server logs. Needs the same setup as run_build, plus network access to a live Visual Builder backend; failures include a plain-language hint. |
| vbcs_list_applicationsA | List applications on a standalone VBCS instance via its REST API (VBCS_BASE_URL). For VBCS apps not backed by a VB Studio git repo. |
| vbcs_lock_applicationA | Lock a live application on a standalone VBCS instance (do this before exporting/importing its data). |
| vbcs_unlock_applicationC | Unlock a locked live application on a standalone VBCS instance. |
| vbcs_export_bo_dataA | Export business-object data from a standalone VBCS instance: one object as CSV (returned inline unless outputPath is given), or omit boName to export every object as a ZIP of CSVs (always saved to disk; path returned). |
| vbcs_import_bo_dataA | Import business-object data into a standalone VBCS instance from a local .csv/.xls/.xlsx (one object; file name must equal the object id) or .zip (several). |
| vbstudio_trigger_buildA | Start a VB Studio CI job (also how you run a deploy job/pipeline step) via the documented Builds REST API. Returns the build number. The API base is derived from the repo's git remote. Credentials: VBSTUDIO_API_TOKEN, or VBSTUDIO_API_USERNAME/PASSWORD (falling back to the git credentials). |
| vbstudio_build_statusB | Get the status (e.g. SUCCESSFUL) of a VB Studio CI build from its job name and build number. |
| vbstudio_job_paramsA | Get a parameterized VB Studio CI job's parameter definitions (YAML), to build the paramsYaml for vbstudio_trigger_build. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 24 tools
Most tools target clearly distinct resources and actions, and descriptions are explicit about scope. The only near-collisions are name-level: list_apps (repo web apps) vs vbcs_list_applications (live standalone VBCS apps), and run_build (local grunt) vs vbstudio_trigger_build (CI job), but the descriptions disambiguate them well.
All names are snake_case with functional prefixes (git_, vbcs_, vbstudio_) that map cleanly to subsystems, mostly following verb_noun. Minor deviations exist: 'doctor' is a bare noun and 'vbstudio_job_params' lacks a verb, but the pattern remains highly readable.
24 tools is on the heavy side, but the server spans five distinct areas (git, artifacts, build, standalone VBCS, CI), each with roughly 3-6 well-differentiated tools. Each tool appears to earn its place; the count is justified by the broad bridge scope rather than padding.
Core workflows are covered (clone/commit/push, read/write/search artifacts, build+audit, live VBCS export/import, CI trigger/status). However, there are notable gaps: no delete_artifact, no git diff/log/branch operations, and no way to cancel or list CI builds/jobs, which will force agents into dead ends for cleanup and inspection tasks.