Skip to Main Content
Shape the future of IBM watsonx Orchestrate

Start by searching and reviewing ideas others have posted, and add a comment (private if needed), vote, or subscribe to updates on them if they matter to you.

If you can't find what you are looking for, create a new idea:

  1. stick to one feature enhancement per idea

  2. add as much detail as possible, including use-case, examples & screenshots (put anything confidential in Hidden details field or a private comment)

  3. Explain business impact and timeline of project being affected

[For IBMers] Add customer/project name, details & timeline in Hidden details field or a private comment (only visible to you and the IBM product team).

This all helps to scope and prioritize your idea among many other good ones. Thank you for your feedback!

Specific links you will want to bookmark for future use
Learn more about IBM watsonx Orchestrate - Use this site to find out additional information and details about the product.
Welcome to the IBM Ideas Portal (https://www.ibm.com/ideas) - Use this site to find out additional information and details about the IBM Ideas process and statuses.
IBM Unified Ideas Portal (https://ideas.ibm.com) - Use this site to view all of your ideas, create new ideas for any IBM product, or search for ideas across all of IBM.
ideasibm@us.ibm.com - Use this email to suggest enhancements to the Ideas process or request help from IBM for submitting your Ideas.

Status Planned for future release
Created by Guest
Created on Dec 3, 2025

Refresh list of Remote MCP tools

In the current implementation of the Remote MCP Server, the list of available tools is cached locally and does not automatically reflect updates made on the server side. This leads to inconsistencies between the actual tool availability and what is presented to users, resulting in operational inefficiencies and potential errors during orchestration.

Users interacting with the Remote MCP Server often encounter outdated tool lists due to the lack of a dynamic refresh mechanism


As a builder, I should be able to refresh the Remote MCP Server tool list when changes are made on the server,

This should cover

  1. New tool added in Remote MCP Server

  2. Tools deleted in Remote MCP Server

  3. Tools updated (Description, Field name, Input and Output Spec) in Remote MCP Server

If a tool is not removed in Remote MCP Server, while refresh the tool should not be removed and reloaded in the tenant, because that will delete the tool from all agents where it is already in use.