Description
MCP prompts that have only optional arguments (all marked as required: false) cannot be invoked through Claude's interface without providing at least one argument. This affects all prompts in the MCP server, making them unusable without workarounds like sending a placeholder value (e.g., ".").
Context
- Project area: mcp-server prompts system
- Complexity: 3/10 - Configuration/compatibility issue
- Related to: MCP SDK integration with Claude Code
Technical Details
All prompt YAML files in mcp-server/src/templates/prompts/ currently define arguments with required: false:
- create_issue.yaml
- create_pr.yaml
- create_commit.yaml
- work_issue.yaml
- refine_pr.yaml
- check_activity.yaml
- create_changelog.yaml
- create_prompt.yaml
The MCP protocol or Claude's handling may have changed to require at least one argument when invoking prompts.
Requirements
- Investigate if this is a Claude Code limitation or MCP protocol requirement
- Check Claude Code GitHub issues for similar reports
- Determine appropriate fix:
- If Claude Code issue: Report upstream and implement workaround
- If our implementation: Update prompt definitions to have at least one required argument where appropriate
Implementation Steps
Acceptance Criteria
Description
MCP prompts that have only optional arguments (all marked as
required: false) cannot be invoked through Claude's interface without providing at least one argument. This affects all prompts in the MCP server, making them unusable without workarounds like sending a placeholder value (e.g., ".").Context
Technical Details
All prompt YAML files in
mcp-server/src/templates/prompts/currently define arguments withrequired: false:The MCP protocol or Claude's handling may have changed to require at least one argument when invoking prompts.
Requirements
Implementation Steps
Acceptance Criteria