-
Notifications
You must be signed in to change notification settings - Fork 166
Add MCP Server Implementation #2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Open
ulasbilgen
wants to merge
6
commits into
rizethereum:main
Choose a base branch
from
ulasbilgen:main
base: main
Could not load branches
Branch not found: {{ refName }}
Loading
Could not load tags
Nothing to show
Loading
Are you sure you want to change the base?
Some commits from the old base branch may be removed from the timeline,
and old review comments may become outdated.
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- Implement Node.js TypeScript MCP server with 6 tools - Add npm package configuration for distribution - Include built files for direct GitHub installation - Update documentation with dual installation options - Maintain backward compatibility with slash commands 🤖 Generated with Claude Code Co-Authored-By: Claude <[email protected]>
- Remove complex GitHub direct install instructions - Emphasize npm package installation as primary method - Simplify user experience with working npm package 🤖 Generated with Claude Code Co-Authored-By: Claude <[email protected]>
- No longer needed since using regular npm registry - Cleanup for cleaner repository 🤖 Generated with Claude Code Co-Authored-By: Claude <[email protected]>
- Add settings configuration for discovery and expert question counts (1-20 range) - Implement MCP elicitation for interactive boolean questions with default handling - Add requirements-settings tool to manage question counts - Update requirements-start to use configurable settings - Rewrite requirements-status with elicitation workflow - Add question pool system with smart defaults and reasoning - Store settings in requirements/.mcp-settings.json - Fix default handling for "press Enter" behavior in MCP clients - Version bump to 1.1.0 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <[email protected]>
- Simplified requirements-settings tool to be parameter-free - Shows current values and asks for each setting separately - Uses MCP elicitation with current values as defaults - Press Enter to keep existing values, or type new number - Clear feedback showing what changed vs unchanged - Better range validation (1-20) with helpful descriptions - Version bump to 1.2.0 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <[email protected]>
- Ensure requirements directory exists in loadSettings() before reading - Fixes issue where settings command fails on fresh projects - Version bump to 1.2.1 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <[email protected]>
amittell
added a commit
to amittell/claude-code-requirements-builder
that referenced
this pull request
Jun 29, 2025
amittell
added a commit
to amittell/claude-code-requirements-builder
that referenced
this pull request
Jun 29, 2025
- Added complete MCP server implementation from PR rizethereum#2 - Added /synthesize command from PR rizethereum#3 - Resolved README.md conflicts by combining both features - Updated package.json URLs for forked repository - All functionality tested and working
justi
added a commit
to justi/claude-code-requirements-builder
that referenced
this pull request
Aug 12, 2025
…re-openai-api-with-gem Integrate OpenAI sentence expansion
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
This PR adds a complete MCP server implementation to the Claude Requirements Gathering System, providing an alternative to the existing slash commands while maintaining full backward compatibility.
🚀 New Features
requirements-start
- Begin new requirement gatheringrequirements-status
- Check progress and session staterequirements-current
- View active requirement detailsrequirements-end
- Complete/incomplete/delete sessionrequirements-list
- Multi-requirement overview with statusrequirements-remind
- Workflow rules and best practices reminderclaude-code-requirements
for easy installation🛠 Technical Implementation
@modelcontextprotocol/sdk
npx claude-code-requirements
📦 Installation
Users can now install via npm:
And add to Claude Desktop config:
✅ Testing
📋 Files Added
src/index.ts
- Main MCP server implementation (564 lines)package.json
- npm package configurationtsconfig.json
- TypeScript configurationdist/
- Built JavaScript files for distributionThis enhancement makes the requirements gathering system accessible to a broader audience while preserving the original slash command functionality for existing users.
🔗 npm Package
Published and working: https://www.npmjs.com/package/claude-code-requirements
🤖 Generated with Claude Code
Co-Authored-By: Claude [email protected]