watsonx MCP Server
Related Servers
Alternatives to watsonx MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityNot gradedmaintenanceEnables Claude to delegate tasks to IBM watsonx.ai foundation models (Granite, Llama, Mistral) for text generation, chat, embeddings, and document analysis. Supports two-agent architectures where Claude can leverage IBM's enterprise AI capabilities for specialized workloads.1-
- AlicenseNot gradedqualityDmaintenanceEnables Claude Code to consult Gemini for complex coding problems with session management, file attachments, and conversation persistence.106MIT
- -licenseNot gradedqualityNot gradedmaintenanceGives Claude access to multiple AI models (Gemini, OpenAI, OpenRouter, Ollama) for enhanced development capabilities including extended reasoning, collaborative development, code review, and advanced debugging.-
- FlicenseNot gradedqualityNot gradedmaintenanceGives Claude Desktop access to multiple AI models (Gemini, OpenAI, OpenRouter, Ollama) for enhanced development capabilities including extended reasoning, collaborative development, code review, debugging, and large context analysis with conversation threading.23 npm1-
- AlicenseNot gradedqualityCmaintenanceEnables Claude Code and Claude Desktop to delegate coding tasks to any model available in OpenCode while Claude remains the orchestrator, planning work, reviewing diffs, and running tests. Supports synchronous and async delegation, model selection, session continuation, and permission-aware execution.2MIT
- AlicenseAqualityBmaintenanceEnables Claude Code to delegate agent tasks to local LLMs via llama.cpp or vLLM servers on your own hardware, reducing API usage while maintaining full agent capabilities.1113MIT
TDQS
Scored across 13 tools
Each tool targets a distinct resource and action: AI generation/embeddings/chat, key lifecycle operations, and z/OS Connect service interactions. Even within similar actions like list_models vs list_keys, the domains are clearly separated by prefixes and descriptions, leaving no ambiguity.
The naming uses consistent lowercase snake_case with clear subservice prefixes (watsonx_, key_protect_, zos_connect_). However, verb placement is not uniform: some tools start with a verb (watsonx_generate, key_protect_list_keys) while others are noun-only (watsonx_embeddings). This minor inconsistency is easy to adapt to.
With 13 tools spanning three related enterprise AI and mainframe domains, the count is well within the ideal range. Each tool handles a distinct operation without redundancy or excessive granularity, making the set easy to learn and use.
Each sub-domain has solid coverage: watsonx generation, chat, embeddings, and model listing; key management covers CRUD plus wrap/unwrap; z/OS Connect supports listing, fetching specs, and calling services. Minor gaps like key rotation or service deployment exist, but the core workflows are fully supported.