Watson Discovery MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WATSONX_DISCOVERY_URL | Yes | The URL of your Watson Discovery instance. | |
| WATSONX_DISCOVERY_APIKEY | Yes | Your Watson Discovery API key. | |
| WATSONX_DISCOVERY_VERSION | No | The version of Watson Discovery API to use. | 2023-03-31 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_projectsA | Watson Discovery Get ProjectsDescriptionThe Watson Discovery Get Projects tool provides access to IBM Watson Discovery's projects, allowing you to retrieve a list of all available projects in your Watson Discovery instance. This tool returns both the human-readable project names and their corresponding unique identifiers (UUIDs) for use in subsequent operations. FunctionThis tool connects to your IBM Watson Discovery instance using your provided authentication credentials, queries the available projects, and returns structured information about each project. Use Cases
AuthenticationThis tool requires valid IBM Cloud IAM API credentials to access your Watson Discovery instance. Ensure your service account has appropriate permissions to list projects. Output FormatResults are returned as a structured array of project objects, each containing:
|
| list_project_collectionsA | Watson Discovery List Project CollectionsDescriptionThe Watson Discovery List Project Collections return a lists of existing collections for the specified project and returns structured information about each collection FunctionThis tool connects to your IBM Watson Discovery instance using your provided authentication credentials, listing the available collections of a project, and returns structured information about each collection. Use Cases
AuthenticationThis tool requires valid IBM Cloud IAM API credentials to access your Watson Discovery instance. Ensure your service account has appropriate permissions to list collections. Output FormatResults are returned as a structured array of collections objects, each containing:
|
| query_projectA | Watson Discovery Query ProjectDescriptionSearch your data by submitting queries that are written in natural language for the specified project and collections. The query returns a list of documents that match the query criteria. FunctionThis tool connects to your IBM Watson Discovery instance using your provided authentication credentials, listing the available documents of a project and collections, and returns structured information about each document. Use Cases
AuthenticationThis tool requires valid IBM Cloud IAM API credentials to access your Watson Discovery instance. Ensure your service account has appropriate permissions to query projects. Output FormatResults are returned as a structured array of result objects, each containing:
|
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 3 tools
Each tool has a distinct purpose: get_projects lists projects, list_project_collections lists collections for a project, and query_project retrieves documents. There is no overlap or ambiguity.
All tools use snake_case with a consistent verb_noun pattern (get_projects, list_project_collections, query_project). No mixing of styles.
With only 3 tools, the server is quite minimal for a service like Watson Discovery, which typically involves many more operations. However, it provides a basic read-only workflow, so it is borderline acceptable.
The server only supports read operations (list projects, list collections, query). Missing create, update, delete for projects and collections, as well as document management features, leaving significant gaps for agents.