React Development Workflow MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_timeA | Get the current time, optionally in a specific timezone |
| echoA | Echo back a message |
| fetch_zoho_taskB | Fetch task details from Zoho Projects by task ID |
| create_feature_branchB | Create a git branch (feat/ or fix/) based on task details |
| check_sonarqube_issuesB | Check SonarQube for code quality issues in a branch |
| auto_fix_sonarqube_issuesC | Automatically fix common SonarQube issues |
| update_task_statusB | Update task status in Zoho Projects |
| generate_implementation_reportC | Generate a summary report of implementation and fixes |
| commit_and_pushB | Commit changes and push to GitHub branch |
| create_pull_requestB | Create a pull request on GitHub |
| check_pr_statusB | Check the status of a pull request |
| merge_pull_requestC | Merge a pull request |
| create_github_releaseC | Create a release on GitHub |
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 13 tools
Each tool targets a distinct action and resource: GitHub operations (create/check/merge PR, create release), SonarQube (check/fix issues), Zoho (update/fetch task), git (create branch, commit/push), plus reporting and utilities. No two tools have overlapping purposes, even the generic get_time and echo are clearly unique.
All tool names follow a consistent snake_case, verb-first pattern (e.g., create_pull_request, check_sonarqube_issues, fetch_zoho_task). Even compound actions like commit_and_push use a clear verb phrase. The naming is uniform and predictable across all 13 tools.
13 tools is well within the ideal 3-15 range and appropriately scoped for a workflow server that integrates multiple systems (GitHub, SonarQube, Zoho, git). Each tool contributes to the workflow without redundancy, and the count feels neither sparse nor bloated.
The tool surface covers the full development lifecycle from feature branch creation, committing/pushing, creating and merging PRs, releasing, checking/fixing SonarQube issues, and updating Zoho tasks. Minor gaps exist such as updating PR details, adding comments/reviews, or reverting changes, but the core workflow is well covered.