4,500+ servers built on MCP Fusion
Vinkius
watsonx Discovery logo
Vinkius
Claude Code logo

How to Use the watsonx Discovery MCP in Claude Code

Run watsonx Discovery searches in CI/CD pipelines using Claude Code's terminal access.

See Vinkius in Action

Works with every AI agent you already use

…and any MCP-compatible client

watsonx Discovery MCP on Cursor AI Code Editor MCP Client watsonx Discovery MCP on Claude Desktop App MCP Integration watsonx Discovery MCP on OpenAI Agents SDK MCP Compatible watsonx Discovery MCP on Visual Studio Code MCP Extension Client watsonx Discovery MCP on GitHub Copilot AI Agent MCP Integration watsonx Discovery MCP on Google Gemini AI MCP Integration watsonx Discovery MCP on Lovable AI Development MCP Client watsonx Discovery MCP on Mistral AI Agents MCP Compatible watsonx Discovery MCP on Amazon AWS Bedrock MCP Support
MCP Servers - Free for Subscribers
Claude Code

Connect watsonx Discovery MCP to Claude Code

Create your Vinkius account to connect watsonx Discovery to Claude Code and route execution through our secure gateway. The platform manages server hosting, runtime updates, and security layers. Configuration requires no manual server provisioning.

GDPR Free for Subscribers

Running Searches via the MCP Server

Need to check data as part of a pipeline? You use `query_discovery_content` to perform natural language or DQL queries against collections. The output streams directly to standard output, making it perfect for subsequent shell scripting steps.

Listing Content and Collections

As part of a CI/CD job, you first need an inventory check. You list all available data buckets using `list_discovery_collections` and then verify the documents in each one with `list_collection_documents`. This validates that the deployment environment has access to the required source material.

Checking Project Health for Scripts

Before running any job, you should confirm the setup. You check component status using `get_component_settings` and inspect specific files with `get_document_details`. This guarantees that the entire watsonx Discovery environment is stable before deployment.

Setup guide

Set up watsonx Discovery MCP in Claude Code

Prerequisites

  • Claude Code CLI installed (npm install -g @anthropic-ai/claude-code)
  • Active Vinkius subscription with a valid endpoint token
  1. 1

    Run the add command

    Open your terminal and run the command shown on the right. Replace [YOUR_TOKEN_HERE] with your endpoint token from cloud.vinkius.com. Use --scope user to make it available across all projects.

  2. 2

    Verify the connection

    Start a Claude Code session and type /mcp to list connected servers. You should see watsonx-discovery-mcp with a green status indicator.

  3. 3

    Start using tools

    Ask Claude Code something like "Check my latest watsonx Discovery transactions." It will automatically discover and invoke the available watsonx Discovery tools.

Terminal
claude mcp add --transport http watsonx-discovery-mcp https://edge.vinkius.com/[YOUR_TOKEN_HERE]/mcp

Why Choose Vinkius

Vinkius connects your tools to AI with real-time monitoring and automatic cost savings — all from one dashboard.

Real-time monitoring

Live

visibility into every interaction

Connect your favorite tools to your AI and see exactly what's happening — every request, every response, in real time.

Built-in savings

60%

lower AI costs

Vinkius compresses data between your apps and your AI automatically. Lower bills every month — no configuration required.

Single dashboard

One

place for every integration

Every tool your AI connects to, managed from a single screen. One account, complete control.

Common questions about watsonx Discovery MCP in Claude Code

You pipe a command into your shell script calling `query_discovery_content`. You provide the collection ID and query text as arguments. The result is raw, machine-readable output perfect for passing to another tool.
The server handles metadata and content indices across various collections within the project. You interact with these resources by listing them or querying their contents directly from the terminal.
Yes, `query_discovery_content` supports both natural language and DQL queries. You embed this tool call into your shell script to perform complex data lookups during the CI/CD process.
You run `get_component_settings` in a test job. This validates that your environment can authenticate and communicate with all necessary components of the MCP Server.
The server manages access to document metadata and collection identifiers. By scripting the calls, you strictly define which resources are queried during your automated pipeline runs.

Start using the watsonx Discovery MCP today

We host it, we monitor it, we maintain it. You just paste one token.

Built & Managed by Vinkius 30s setup 6 tools

We've already built the connector for watsonx Discovery. Just plug in your AI agents and start using Vinkius.

No hosting. No infrastructure. No complex setup.
All 6 tools are live and waiting. You're up and running in seconds.

Claude Claude
ChatGPT ChatGPT
Cursor Cursor
Gemini Gemini
Windsurf Windsurf
VS Code VS Code
JetBrains JetBrains
Vercel Vercel
+ other MCP clients

Vinkius gives your AI agents access to the full catalog of app connectors, all fully managed, secure, and enterprise-ready. One subscription, every tool you need.

Zero hosting required Full MCP catalog included Enterprise-grade security Auto-updated by Vinkius

Built, hosted, and secured by Vinkius. You just connect and go.