Skip to main content
Glama
Sign In
OVB3 Bridge

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
      D
      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.
      55 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
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A3.5/5.0

    Scored across 24 tools

    Disambiguation4/5

    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.

    Naming Consistency4/5

    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.

    Tool Count4/5

    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.

    Completeness3/5

    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.

    Maintenance

    ActivityNo data
    ResponsivenessSyncing

    Resources