[FEATURE] Claude Code CLI MCP Prompts do not elicit user input for prompt arguments

Resolved 💬 5 comments Opened Mar 4, 2026 by CharlieDigital Closed Apr 25, 2026

Preflight Checklist

  • [x] I have searched existing requests and this feature hasn't been requested yet
  • [x] This is a single feature request (not multiple features)

Problem Statement

When an MCP server exposes Prompts (https://modelcontextprotocol.io/specification/2025-03-26/server/prompts) with required arguments/parameters, Claude Code does not ask the user for inputs for these required parameters. This causes the prompt call to time out and fail.

Proposed Solution

When CC uses an MCP prompt,

  • It should read the arguments/parameters and ask the user for values for those parameters.
  • It should show the descriptions for those parameters

Alternative Solutions

The workaround is to explicitly provide the parameters when invoking the tool; however, users may not be aware of the presence of the parameters at all since the user interface does not provide clues that there are parameters required.

Priority

Medium - Would be very helpful

Feature Category

CLI commands and flags

Use Case Example

  1. Provide an MCP server which advertises standard enterprise-wide pre-configured prompts
  2. Prompt has one or more required parameters
  3. User adds the MCP server and sees the prompts when using / command
  4. User attempts to use the prompt without providing any parameters
  5. The MCP server call fails because user does not provide required parameters

Additional Context

https://github.com/user-attachments/assets/c6220e48-d1ea-4ccf-b2ab-2591a0c3f1db

The MCP invoke times out from the missing parameters and fails.

Here is how VS Code GH Copilot handles the same interaction by eliciting the values for the required parameters from the user:

https://github.com/user-attachments/assets/74fc364a-c1ac-43cb-8fd1-d9913008902e

View original on GitHub ↗

This issue has 5 comments on GitHub. Read the full discussion on GitHub ↗