Skip to main content
Glama
watsonx Platform MCP Server

watsonx Platform MCP Server

by manjotsidhu

Related Servers

Alternatives to watsonx Platform MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      A
      maintenance
      Enables AI assistants to interact seamlessly with IBM watsonx.data lakehouses using natural language for operations like querying, catalog browsing, engine management, and data ingestion.
      39
      263 PyPI
      9
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Connects AI assistants directly to IBM Maximo so they can discover APIs, inspect schemas, query live data, generate Carbon UI, and create, update, or act on Maximo records through natural language.
      75 npm
      Apache 2.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to interact with Databricks workspaces programmatically, providing comprehensive tools for cluster management, notebook operations, job orchestration, Unity Catalog data governance, user management, permissions control, and FinOps cost analytics.
      360 npm
      MIT
    • A
      license
      B
      quality
      A
      maintenance
      Enables AI assistants to provision and manage cloud infrastructure and AI/ML workloads—such as GPUs, nodes, storage, networking, databases, Kubernetes, and training/inference resources—through natural language. It also provides a universal REST tool for authenticated access to the underlying cloud API.
      46
      18 npm
      Apache 2.0

    TDQS

    C2.5/5.0

    Scored across 29 tools

    Disambiguation4/5

    Tools are mostly cleanly separated by resource+action (projects, connections, jobs, job runs, assets, members). Some conceptual overlap exists because jobs are a kind of asset (get_job vs get_asset, delete_job but no delete_asset) and the run sub-resources (create/get/list/cancel_job_run) sit close to the job tools, but descriptions clarify intent.

    Naming Consistency4/5

    Nearly all tools follow a predictable verb_noun snake_case pattern (list_projects, create_job_run, delete_connection). Minor deviations: members use add/remove_project_member while other resources use create/delete, and 'authenticate' is a bare verb with no noun.

    Tool Count3/5

    At 29 tools this sits above the comfortable range, and several are flagged EXPERIMENTAL/untested. The breadth is partly justified by covering six distinct sub-domains (projects, connections, jobs, runs, assets, members), but the surface feels heavy and could be trimmed.

    Completeness4/5

    Most resources have full lifecycle coverage: projects (CRUD), connections (CRUD + types), jobs (CRUD), job runs (create/get/list/cancel), and members (list/add/update/remove). The notable gap is generic assets, which have create/get/list but no update or delete, and no job-run logs tool.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues