4,000+ servers built on MCP Fusion
Vinkius
CrewAIFramework
Why use watsonx Discovery MCP Server with CrewAI?

Bring Cognitive Search
to CrewAI

Create your Vinkius account to connect watsonx Discovery to CrewAI and start using all 6 AI tools in minutes. Fully managed, enterprise secure, and ready to use without writing a single line of code. No hosting, no server setup — just connect and start using.

MCP Inspector GDPR Free for Subscribers
Get Component SettingsGet Document DetailsList Available EnrichmentsList Collection DocumentsList Discovery CollectionsQuery Discovery Content
ChatGPT Claude Perplexity

Compatible with every major AI agent and IDE

ClaudeClaude
ChatGPTChatGPT
CursorCursor
GeminiGemini
WindsurfWindsurf
VS CodeVS Code
JetBrainsJetBrains
VercelVercel
+ other MCP clients
watsonx Discovery

What is the watsonx Discovery MCP Server?

Connect your IBM watsonx Discovery account to any AI agent and harness the power of cognitive search and NLP-driven text analytics through natural conversation.

What you can do

  • Cognitive Search — Perform natural language or Discovery Query Language (DQL) queries against your data collections for high-quality semantic search
  • Data Discovery — Browse and list all data collections within your project to retrieve collection and document IDs
  • Document Analysis — Retrieve comprehensive metadata, ingestion status, and technical details for specific indexed documents
  • NLP Enrichments — List and monitor available enrichments (NLP models) like Sentiment, Entities, and Keywords being applied to your data
  • Component Health — Verify project-level configurations, ingestion notices, and health settings for all project components
  • Semantic Insights — Surface relevant information and hidden patterns from massive unstructured datasets through simple chat commands

How it works

  1. Subscribe to this server
  2. Enter your watsonx URL, API Key, and Project ID
  3. Start querying your cognitive data collections through Claude, Cursor, or any MCP-compatible client

No more manual digging through complex IBM Cloud consoles to query your data. Your AI agent becomes your cognitive data scientist.

Who is this for?

  • Enterprise Developers — build grounded AI applications using Discovery's semantic search and ingestion pipelines
  • Knowledge Analysts — quickly surface information from large document repositories and audit NLP enrichments
  • Data Scientists — test and refine DQL queries and monitor data ingestion status through chat
  • Product Teams — implement AI-powered search features and monitor the health of your discovery project

Built-in capabilities (6)

get_component_settings

Retrieves the configuration and health settings for project components

get_document_details

Retrieves metadata and status for a specific indexed document

list_available_enrichments

g., Sentiment, Entities) are being applied to documents. Lists all enrichments (NLP models) configured for the project

list_collection_documents

Lists all documents indexed within a specific collection

list_discovery_collections

Lists all data collections within the current watsonx Discovery project

query_discovery_content

Provide a collection ID and the query text. Performs a natural language or DQL query against a discovery collection

Why CrewAI?

When paired with CrewAI, watsonx Discovery becomes a first-class tool in your multi-agent workflows. Each agent in the crew can call watsonx Discovery tools autonomously, one agent queries data, another analyzes results, a third compiles reports, all orchestrated through Vinkius with zero configuration overhead.

  • Multi-agent collaboration lets you decompose complex workflows into specialized roles, one agent researches, another analyzes, a third generates reports, each with access to MCP tools

  • CrewAI's native MCP integration requires zero adapter code: pass Vinkius Edge URL directly in the mcps parameter and agents auto-discover every available tool at runtime

  • Built-in task delegation and shared memory mean agents can pass context between steps without manual state management, enabling multi-hop reasoning across tool calls

  • Sequential and hierarchical crew patterns map naturally to real-world workflows: enumerate subdomains → analyze DNS history → check WHOIS records → compile findings into actionable reports

See it in action

watsonx Discovery in CrewAI

AI AgentVinkius
High Security·Kill Switch·Plug and Play
Enterprise Security

Why run watsonx Discovery with Vinkius?

The watsonx Discovery connection runs on our fully managed, secure cloud infrastructure. We handle the hosting, maintenance, and security so you don't have to deal with servers or code. All 6 tools are ready to work instantly without any complex setup.

You stay in complete control of your data. Your AI only accesses the information you approve, keeping your sensitive passwords and private details completely safe. Plus, with automatic optimizations, your AI works faster and more efficiently.

watsonx Discovery
Fully ManagedNo server setup
Plug & PlayNo coding needed
SecurePrivacy protected
PrivateYour data is safe
Cost ControlBudget limits
Control1-click disconnect
Auto-UpdatesMaintenance free
High SpeedOptimized for AI
Reliable99.9% uptime
Your credentials and connection tokens are fully encrypted

* Every connection is hosted and maintained by Vinkius. We handle the security, updates, and infrastructure so you don't have to write code or manage servers. See our infrastructure

01 / Catalog

Over 4,000 integrations ready for AI agents

Explore a vast library of pre-built integrations, optimized and ready to deploy.

02 / Credentials

Connect securely in under 30 seconds

Generate tokens to authenticate and link external services in a single step.

03 / Guardian

Complete visibility into every agent action

Audit live requests, latency, success rates, and active security compliance policies.

04 / FinOps

Optimize spending and track token ROI

Analyze real-time token consumption and cost metrics detailed by connection.

Over 4,000 integrations ready for AI agents
Connect securely in under 30 seconds
Complete visibility into every agent action
Optimize spending and track token ROI

Explore our live AI Agents Analytics dashboard to see it all working

This dashboard is included when you connect watsonx Discovery using Vinkius. You will never be left in the dark about what your AI agents are doing with your tools.

Why Vinkius

watsonx Discovery and 4,000+ other AI tools. No hosting, no code, ready to use.

Professionals who connect watsonx Discovery to CrewAI through Vinkius don't need to write code, manage servers, or worry about security. Everything is pre-configured, secure, and runs automatically in the background.

4,000+MCP Integrations
<40msResponse time
100%Fully managed
Raw MCP
Vinkius
Ready-to-use MCPsFind and configure each manually4,000+ MCPs ready to use
Connection SetupManual coding & server setup1-click instant connection
Server HostingYou host it yourself (needs 24/7 uptime)100% hosted & managed by Vinkius
Security & PrivacyStored in plaintext config filesBank-grade encrypted vault
Activity VisibilityBlind execution (no logs or tracking)Live dashboard with real-time logs
Cost ControlRunaway AI token spend riskAutomatic budget limits
Revoking AccessMust delete files or code to stop1-click disconnect button
The Vinkius Advantage

How Vinkius secures watsonx Discovery for CrewAI

Every request between CrewAI and watsonx Discovery is protected by our secure gateway. We automatically keep your sensitive data private, prevent unauthorized access, and let you disconnect instantly at any time.

< 40msCold start
Ed25519Signed audit chain
60%Token savings
FAQ

Frequently asked questions

01

Can I query my data collections using natural language?

Yes. The query_discovery_content tool allows your AI agent to perform natural language queries against your watsonx Discovery collections, returning highly relevant results based on IBM's cognitive search engine.

02

How do I see what NLP models are being applied to my documents?

Use the list_available_enrichments tool to see all NLP enrichments (like Sentiment, Entity Extraction, or Category Classification) configured for your project and applied during the ingestion pipeline.

03

Can I monitor the ingestion status of a specific document?

Absolutely. Using the get_document_details tool, you can check the ingestion status and technical metadata for any specific document ID, ensuring your data is correctly indexed and searchable.

04

How does CrewAI discover and connect to MCP tools?

CrewAI connects to MCP servers lazily. when the crew starts, each agent resolves its MCP URLs and fetches the tool catalog via the standard tools/list method. This means tools are always fresh and reflect the server's current capabilities. No tool schemas need to be hardcoded.

05

Can different agents in the same crew use different MCP servers?

Yes. Each agent has its own mcps list, so you can assign specific servers to specific roles. For example, a reconnaissance agent might use a domain intelligence server while an analysis agent uses a vulnerability database server.

06

What happens when an MCP tool call fails during a crew run?

CrewAI wraps tool failures as context for the agent. The LLM receives the error message and can decide to retry with different parameters, fall back to a different tool, or mark the task as partially complete. This resilience is critical for production workflows.

07

Can CrewAI agents call multiple MCP tools in parallel?

CrewAI agents execute tool calls sequentially within a single reasoning step. However, you can run multiple agents in parallel using process=Process.parallel, each calling different MCP tools concurrently. This is ideal for workflows where separate data sources need to be queried simultaneously.

08

Can I run CrewAI crews on a schedule (cron)?

Yes. CrewAI crews are standard Python scripts, so you can invoke them via cron, Airflow, Celery, or any task scheduler. The crew.kickoff() method runs synchronously by default, making it straightforward to integrate into existing pipelines.

09

MCP tools not discovered

Ensure the Edge URL is correct. CrewAI connects lazily when the crew starts. check console output.

10

Agent not using tools

Make the task description specific. Instead of "do something", say "Use the available tools to list contacts".

11

Timeout errors

CrewAI has a 10s connection timeout by default. Ensure your network can reach the Edge URL.

12

Rate limiting or 429 errors

Vinkius enforces per-token rate limits. Check your subscription tier and request quota in the dashboard. Upgrade if you need higher throughput.

Explore More MCP Servers

View all →