React Development Workflow MCP Server
Allows creating Git branches with proper naming conventions (feat/ or fix/) based on task information.
Provides tools to check for code quality issues in a branch and automatically fix common SonarQube issues.
Enables fetching task details from Zoho Projects and updating task status (Open, In Progress, Completed).
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@React Development Workflow MCP Server Fetch Zoho task 123 and create a feature branch."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
React Development Workflow MCP Server
A Model Context Protocol (MCP) server implementation in TypeScript that streamlines the React development workflow by integrating Zoho Projects, Git, and SonarQube tools.
What is MCP?
The Model Context Protocol (MCP) is a standard for connecting AI assistants with data sources and tools. This server provides an integrated workflow for React developers to manage tasks, create branches, and ensure code quality in real-time.
Related MCP server: Error Tracker MCP Server
Features
This server provides the following tools:
Core Workflow Tools
fetch_zoho_task: Fetch task details from Zoho Projects by task ID
create_feature_branch: Create git branches (feat/ or fix/) based on task information
check_sonarqube_issues: Check for SonarQube code quality issues in a branch
auto_fix_sonarqube_issues: Automatically fix common SonarQube issues detected in code
update_task_status: Update task status in Zoho Projects (Open, In Progress, Completed)
generate_implementation_report: Generate a summary report of implementation and quality fixes
Utility Tools
get_time: Get the current time, optionally in a specific timezone
echo: Echo back a message
Workflow Overview
The typical workflow is:
fetch_zoho_task - Retrieve task details from Zoho Projects
create_feature_branch - Create a git branch with proper naming convention
Check code during implementation - While implementing, continuously use check_sonarqube_issues
auto_fix_sonarqube_issues - Fix detected quality issues in real-time
update_task_status - Update Zoho with progress
generate_implementation_report - Create a final report of work completed
Installation
Clone this repository
Install dependencies:
npm install
Building
Build the TypeScript code:
npm run buildSetup & Configuration
Before using this MCP, you need to set up:
Zoho Projects - API credentials for fetching tasks
SonarQube - Project configuration and authentication token
Git - User configuration for branch creation
See CONFIGURATION.md for detailed setup instructions.
⚠️ Security: Always keep credentials in .env.local (not committed). See SECURITY.md for best practices.
Usage
Quick Start
Configure credentials (see CONFIGURATION.md)
Start the MCP server:
npm startUse with Claude Code by adding to
.claude/settings.json
Running the Server
npm startOr for development with automatic rebuilding:
npm run devThe server will run on stdio and communicate using the MCP protocol.
Workflow Example
See WORKFLOW.md for a complete example of how to use this MCP in your React development workflow.
Using with VS Code
This project includes a .vscode/mcp.json configuration file that allows you to debug the MCP server directly in VS Code. The server will be available as "workflow-mcp" in your MCP client.
Development
Project Structure
mcp-demo/
├── src/
│ └── index.ts # Main server implementation
├── build/ # Compiled JavaScript (generated)
├── .github/
│ └── copilot-instructions.md # GitHub Copilot instructions
├── .vscode/
│ └── mcp.json # VS Code MCP configuration
├── package.json
├── tsconfig.json
└── README.mdAdding New Tools
To add a new tool:
Define a Zod schema for input validation
Add the tool definition to the
ListToolsRequestSchemahandlerImplement the tool logic in the
CallToolRequestSchemahandler
Example:
// 1. Define schema
const MyToolSchema = z.object({
input: z.string().describe("Input parameter"),
});
// 2. Add to tools list
{
name: "my_tool",
description: "Description of what the tool does",
inputSchema: {
type: "object",
properties: {
input: {
type: "string",
description: "Input parameter",
},
},
required: ["input"],
},
}
// 3. Handle the tool call
case "my_tool": {
const parsed = MyToolSchema.parse(args);
return {
content: [
{
type: "text",
text: `Result: ${parsed.input}`,
},
],
};
}Dependencies
@modelcontextprotocol/sdk: MCP SDK for TypeScript
zod: Schema validation library
typescript: TypeScript compiler
@types/node: Node.js type definitions
Scripts
npm run build- Compile TypeScript to JavaScriptnpm start- Run the compiled servernpm run dev- Build and run the servernpm test- Run tests (placeholder)
License
ISC
Documentation
CONFIGURATION.md - Setup and configuration guide
WORKFLOW.md - Complete workflow examples
TOOLS.md - Detailed tool reference
External Resources
About This Project
This MCP was built to solve a real React development workflow problem:
The Problem: Developers waste 2-3 hours per week context-switching between Zoho Projects, Git, and SonarQube while implementing features.
The Solution: A single integrated MCP that:
Fetches tasks from Zoho
Creates proper git branches
Continuously checks code quality
Fixes issues in real-time
Updates task status automatically
Generates implementation reports
Time Saved: 2-3 hours per week per developer
Available Tools
13 toolsauto_fix_sonarqube_issuesC
Automatically fix common SonarQube issues
Inputs: issues (required), fileType.
check_pr_statusB
Check the status of a pull request
Inputs: branchName (required).
check_sonarqube_issuesB
Check SonarQube for code quality issues in a branch
Inputs: projectKey (required), branchName.
commit_and_pushB
Commit changes and push to GitHub branch
Inputs: branch (required), message (required), files.
create_feature_branchB
Create a git branch (feat/ or fix/) based on task details
Inputs: type (required), taskId (required), taskName (required).
create_github_releaseC
Create a release on GitHub
Inputs: tag (required), body (required), title (required), draft.
create_pull_requestB
Create a pull request on GitHub
Inputs: body (required), title (required), sourceBranch (required), draft, +1 more.
echoA
Echo back a message
Inputs: message (required).
fetch_zoho_taskB
Fetch task details from Zoho Projects by task ID
Inputs: taskId (required), projectKey.
generate_implementation_reportC
Generate a summary report of implementation and fixes
Inputs: taskId (required), taskName (required), branchName (required), issuesFixed (required), +1 more.
get_timeA
Get the current time, optionally in a specific timezone
Inputs: timezone.
merge_pull_requestC
Merge a pull request
Inputs: branchName (required), mergeStrategy, deleteAfterMerge.
update_task_statusB
Update task status in Zoho Projects
Inputs: status (required), taskId (required), message.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
Track stories, organize sprints, and manage project workflows across your team
GitHub security scanning, code audit, and workflow automation for repositories.
DORA OS Conductor — 16-tool meta-orchestrator for DORA compliance workflow automation.
Health scores for your team's frontend repos: findings, the fixes worth most points, and SBOMs.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceIntegrates Jira and GitLab to enable AI agents to seamlessly manage issues, create branches, and automate SRE workflows from issue detection to fix deployment. Features AI-powered analysis for intelligent code generation and comprehensive automation across both platforms.-
- AlicenseNot gradedqualityDmaintenanceAutomates error tracking workflow by finding code owners in Bitbucket, retrieving related pull requests, and creating assigned JIRA tickets for code errors.6 npmMIT
- AlicenseBqualityDmaintenanceEnables execution of terminal commands, git operations, and automated setup of React, Vue, and Next.js projects with VSCode integration.775 npmMIT
- AlicenseBqualityDmaintenanceAutomates the conversion of Figma designs into TypeScript React components and integrates with GitHub to create pull requests for the generated code. It includes visual regression testing with Playwright and accessibility validation to ensure implementations match the original designs.529 npmMIT