Skip to main content
Glama
vanamthrishul

OVB3 Bridge

by vanamthrishul
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to OVB3 Bridge

No user-submitted related servers found.

    Related Servers

    • Workato Dev MCP

      gmunro-lyft
      F
      license
      B
      quality
      C
      maintenance
      A local, zero-dependency MCP server to author, lint, deploy, and debug Workato recipes from Claude. It wraps the Workato Developer REST API, RLCM package API, and Data Tables record API with 56 tools.
      56
      -

    • visdemo-fusion-mcp

      yedla26
      F
      license
      Not graded
      quality
      D
      maintenance
      MCP server that connects Claude Desktop to an Oracle Fusion Cloud instance. It exposes suppliers, purchase orders, invoices, and project costs as callable tools.
      -

    • salesforce-mcp

      ryu-727
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that provides comprehensive access to Salesforce Tooling API for metadata management, SOQL queries, code analysis, and debugging through Claude and other AI assistants.
      31 npm
      5
      MIT

    • workday-studio-mcp

      andrew-price-huron
      F
      license
      Not graded
      quality
      C
      maintenance
      A local MCP server that gives Claude direct access to Workday Studio workspace. Enables reading, writing, planning, and validating integration assemblies without network calls or tenant credentials.
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.3/5.0

    Scored across 19 tools

    Disambiguation5/5

    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.

    Naming Consistency4/5

    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.

    Tool Count4/5

    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.

    Completeness3/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources