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 |
|---|---|
| list_reposA | List local VB Studio project repo checkouts discoverable under VBS_WORKSPACE_DIR. |
| list_appsA | List VBCS web app names (webApps/) present in a repo checkout. |
| read_artifactA | Read a VBCS artifact file (page/flow/chain/service JSON, etc) by repo-relative path. |
| write_artifactA | Write a VBCS artifact file by repo-relative path. Refuses invalid JSON for .json paths. |
| list_artifactsA | List artifact files in a repo matching a glob pattern, e.g. 'webApps//flows/**/.json'. |
| git_statusA | Show git status for a repo checkout. |
| git_commitC | Stage and commit changes in a repo checkout. |
| git_pullC | Pull from the repo's remote. |
| git_pushC | Push to the repo's remote. |
| git_cloneA | Clone a git remote into VBS_WORKSPACE_DIR so it's discoverable by list_repos. Used by /link's VBS setup flow. |
| run_buildA | Run grunt-vb-build for a VBCS app. Streams output live to server logs as it runs. |
| run_auditA | Run grunt-vb-audit for a VBCS app. Streams output live to server logs as it runs. |
| 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_applicationC | Lock a live application on a standalone VBCS instance. |
| vbcs_unlock_applicationC | Unlock a live application on a standalone VBCS instance. |
| vbcs_export_bo_dataC | Export a business object's data records from a standalone VBCS instance. |
| vbstudio_list_projectsA | [NOT IMPLEMENTED] List VB Studio projects on the instance. Blocked until a live dev instance is confirmed. |
| vbstudio_trigger_buildC | [NOT IMPLEMENTED] Trigger a CI/CD build via the VB Studio REST API. Blocked until a live dev instance is confirmed. |
| vbstudio_trigger_deployC | [NOT IMPLEMENTED] Trigger a deploy via the VB Studio REST API. Blocked until a live dev instance is confirmed. |
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 19 tools
Each tool targets a distinct resource and action: repo listing, artifact CRUD, git operations, build/audit, and VBCS/VB Studio REST calls are all clearly separated. Even similarly named tools like list_apps and vbcs_list_applications are distinguished by their local vs remote scope.
Most tools follow a clear verb_noun pattern (list_repos, read_artifact, run_build), and the git_*, vbcs_*, and vbstudio_* prefixes provide meaningful grouping. However, git_* tools use a noun_verb style (git_status, git_commit) that deviates from the primary pattern, slightly reducing overall consistency.
At 19 tools, the server is slightly above the typical 3-15 well-scoped range, but the breadth covers local repo management, build tooling, and two distinct remote APIs. The three [NOT IMPLEMENTED] tools add to the count without contributing functionality, but the overall scope justifies the number.
The core bridge workflows are covered: get local repo status, commit/pull/push, read/write artifacts, build, and interact with standalone VBCS apps. However, the VB Studio integration is entirely unimplemented, and there are no artifact delete/update operations or BO data mutation, leaving notable gaps for a comprehensive bridge.