Konnexx Development MCP Server
OfficialProvides commands for Flutter mobile projects including implementing features and committing PRs.
Provides tools for committing changes and creating pull requests on GitHub repositories.
Provides commands for Laravel API projects including implementing features, running tests, architecture reviews, and committing PRs.
Provides commands for Next.js web projects including implementing features, running tests, architecture reviews, and committing PRs.
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., "@Konnexx Development MCP Server Use implement_feature for ticket ABC-123"
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.
Konnexx Development MCP Server
Centralized command server for all Konnexx projects - One npm package, works across all your Laravel, Next.js, Architecture, and Flutter projects. No more copying commands to each project!
๐ฏ What Is This?
This is an MCP (Model Context Protocol) server that provides standardized development workflow commands to Cursor AI. Instead of maintaining commands in each project's .cursor folder, you install this package once globally and use it everywhere.
Key Benefits:
โ One install, all projects - Install globally, works everywhere
โ Auto-detection - Automatically detects project type (Laravel, Next.js, Architecture, Flutter)
โ Team-wide consistency - Everyone uses the same commands
โ Easy updates - Update once, team gets it automatically (with remote commands)
โ Version controlled - Commands stored as markdown files in Git
Related MCP server: MCP SDD Server
๐ Quick Start (3 Steps)
Step 1: Install Globally
npm install -g konnexx-dev-mcpStep 2: Configure Cursor
Open Cursor Settings โ Features โ MCP and add:
{
"mcpServers": {
"konnexx-dev": {
"command": "konnexx-dev-mcp"
}
}
}Step 3: Restart Cursor & Test
Restart Cursor completely, then in any project, type in AI chat:
Use verify_mcp_serversThat's it! The MCP server will auto-detect your project type and show relevant commands.
โ Verifying Tool Access
Quick Verification (From Any Project)
Run this command from any project directory to verify installation and see expected tools:
# From the konnexx-dev-mcp package directory
npm run verify
# OR from any project (if you have the package locally)
npx konnexx-dev-mcp verifyThis will:
โ Check if
konnexx-dev-mcpis installed globallyโ Detect your project type (API, Web, Mobile, Architecture)
โ Show which tools should be available
โ Provide instructions for testing in Cursor
Verifying in Cursor
Method 1: Use the verify command
Open Cursor in your project
In AI chat, type:
Use verify_mcp_serversThis will test all MCP servers and show their status
Method 2: Test a specific tool
Open Cursor in your project (e.g., a Laravel API project)
In AI chat, type:
Use implement_featureIf the tool is available, Cursor will show it in autocomplete
Provide the ticket:
Ticket: Add user authentication featureThe tool should execute and start the workflow
Method 3: Check tool list
Open Cursor
Open MCP panel (usually in the sidebar or settings)
Look for
konnexx-devserverCheck the tools list - you should see tools like
implement_feature,commit_pr, etc.
Troubleshooting
Tools not appearing?
โ Restart Cursor completely (not just reload window)
โ Check Cursor Settings โ Features โ MCP โ
konnexx-devis configuredโ Verify installation:
npm list -g konnexx-dev-mcpโ Check MCP server logs in Cursor's MCP panel for errors
Project type not detected?
โ For API: Ensure
composer.jsoncontains"laravel/framework"inrequireโ For Web: Ensure
package.jsoncontains"next"independenciesโ For Mobile: Ensure
pubspec.yamlexists in project rootโ For Architecture: Ensure project path contains "architecture"
Tool executes but shows error?
โ Check that command markdown files exist in the
commands/directoryโ Verify MCP server can access the commands directory
โ Check MCP server logs for file path issues
๐ Available Commands
The server automatically detects your project type and shows only relevant commands. Total: 26 commands across all project types.
How to Use Commands:
Simply type
Use {command_name}in Cursor AI chat (e.g.,Use implement_featureorUse commit_pr)Commands are automatically available based on your project type
No parameters needed for most commands - they'll prompt you if needed
๐๏ธ Architecture Projects (8 commands)
Detected when: Project path contains "architecture" or no framework detected
Command | Parameters | Description |
|
| Generate development tickets in batches of 5 |
|
| Generate multiple ticket batches for phases |
| None | Design Entity-Relationship Diagram from requirements |
| None | Extract and structure requirements from documentation |
| None | Specify API endpoints from requirements and ERD |
| None | Create timeline and Gantt chart |
| None | Orchestrate complete architecture workflow |
| None | Commit changes and create PR |
๐ง API Projects - Laravel (5 commands)
Detected when: composer.json exists + Laravel framework detected
Command | Parameters | Description |
|
| Full feature implementation workflow (plan โ implement โ review โ test) |
|
| Run tests and fix failures using parallel agents |
|
| Run tests incrementally, fixing one at a time |
| None | Review code for architectural compliance (DDD, Laravel patterns) |
| None | Commit changes and create PR |
๐ Web Projects - Next.js (5 commands)
Detected when: package.json exists + Next.js dependency detected
Command | Parameters | Description |
|
| Implement features following 7-step process (Types โ Service โ Hooks โ Components โ Screens โ Routes) |
|
| Run tests and fix failures |
|
| Run tests incrementally, fixing one at a time |
| None | Review code for architectural compliance (Next.js patterns) |
| None | Commit changes and create PR |
๐ฑ Mobile Projects - Flutter (2 commands)
Detected when: pubspec.yaml exists
Command | Parameters | Description |
|
| Implement features for Flutter applications |
| None | Commit changes and create PR |
๐ Shared Commands (7 commands)
Available in every project type:
Command | Parameters | Description |
| None | Verify all MCP servers are working (Context7, GitHub, Filesystem, Database, Browser) |
| None | Clean up Cursor plan files automatically |
|
| Query database using Database MCP |
|
| Look up documentation using Context7 MCP |
| None | Test the konnexx-dev-mcp package locally (builds, creates npm link, validates) |
| None | Publish konnexx-dev-mcp to npm (reviews changes, versions, builds, publishes) |
| None | Commit changes and create PR (auto-detects project type) |
๐ก How It Works
You open a project in Cursor (Laravel API, Next.js web app, Architecture project, etc.)
MCP server auto-detects project type by checking for:
composer.json+ Laravel โ API Projectpackage.json+ Next.js โ Web Projectpubspec.yamlโ Mobile ProjectPath contains "architecture" โ Architecture Project
Server shows relevant commands - Only commands for your project type appear
You use commands in AI chat - Type
Use implement_featureorUse commit_prCommand executes - The server loads the markdown command file and Cursor executes it
๐ฎ How to Use Commands
Basic Usage
Simply type in Cursor AI chat:
Use {command_name}Examples:
Use implement_feature- Start feature implementationUse commit_pr- Commit and create PRUse verify_mcp_servers- Test MCP connectivityUse architecture_review- Review code architecture
Commands with Parameters
Some commands require parameters. When you use them, Cursor will prompt you:
Example:
Use implement_feature
Ticket: Add user authentication featureCommands that need parameters:
implement_feature- requiresticket(string)implement_feature_web- requiresticket(string)implement_feature_mobile- requiresticket(string)db_query- requiresquery(string)docs_lookup- requiresquery(string)generate_tickets- requiresepic(string) andphase(string)generate_tickets_batch- requiresepic(string) andphases(array)
Finding Available Commands
The MCP server automatically shows only commands relevant to your project type. To see all available commands:
Open Cursor AI chat
Type
Useand Cursor will show autocomplete suggestionsOr check the command tables above for your project type
๐ฏ Project Auto-Detection
Detection Criteria | Project Type | Commands Available |
| API (Laravel) |
|
| Web (Next.js) |
|
| Mobile (Flutter) |
|
Path contains "architecture" OR no framework detected | Architecture |
|
Plus shared commands (verify_mcp_servers, clear_plans, db_query, docs_lookup) are available in all project types.
๐ฆ Installation Options
Option 1: npm Global Install (Recommended)
Best for: Team members, production use
npm install -g konnexx-dev-mcpCursor Config:
{
"mcpServers": {
"konnexx-dev": {
"command": "konnexx-dev-mcp"
}
}
}Option 2: With Remote Commands (Always Up-to-Date)
Best for: Teams that want instant updates without npm republishing
Install:
npm install -g konnexx-dev-mcpCursor Config:
{
"mcpServers": {
"konnexx-dev": {
"command": "konnexx-dev-mcp",
"env": {
"KONNEXX_MCP_REMOTE_SOURCE": "https://raw.githubusercontent.com/Konnexx-Software-Developers/konnexx-dev-mcp/main",
"KONNEXX_MCP_USE_REMOTE": "true"
}
}
}
}Benefits:
โ Commands fetched from GitHub on each use
โ Team gets updates automatically (no
npm updateneeded)โ Instant updates when you push to GitHub
Option 3: Local Development
Best for: Developing the MCP server itself
git clone https://github.com/Konnexx-Software-Developers/konnexx-dev-mcp.git
cd konnexx-dev-mcp
npm install
npm run buildCursor Config:
{
"mcpServers": {
"konnexx-dev": {
"command": "node",
"args": ["C:\\path\\to\\konnexx-dev-mcp\\dist\\index.js"]
}
}
}๐ Updating Commands
For Team Leads: Publishing Updates
Quick Update (Remote Commands - Recommended):
# Edit command file
code commands/api/implement-feature.md
# Commit and push
git add commands/api/implement-feature.md
git commit -m "feat: Updated implement-feature workflow"
git push
# โ
Team gets updates automatically!Major Release (npm Package):
# Make changes, then:
npm version patch # or minor/major
npm publish --access public
# Team updates with:
npm update -g konnexx-dev-mcpComplete Guide: See docs/PUBLISHING_WORKFLOW.md for:
Step-by-step publishing workflow
Update methods (remote vs npm)
Team notification templates
Version strategy
Troubleshooting
For Team Members: Getting Updates
If using remote commands: Updates are automatic! Just restart Cursor.
If using npm only:
npm update -g konnexx-dev-mcp
# Then restart Cursor๐ Package Structure
konnexx-dev-mcp/
โโโ commands/ # Command markdown files
โ โโโ api/ # Laravel API commands (5 files)
โ โโโ architecture/ # Architecture commands (8 files)
โ โโโ web/ # Next.js web commands (5 files)
โ โโโ mobile/ # Flutter mobile commands (future)
โ โโโ shared/ # Shared utilities (5 files)
โโโ src/ # MCP server source code
โ โโโ index.ts # Main server implementation
โโโ docs/ # Documentation
โโโ dist/ # Compiled JavaScript (built)
โโโ package.json
โโโ README.mdTotal: 26 command files organized by project type
๐ง Troubleshooting
MCP Server Not Showing in Cursor
Check installation:
npm list -g konnexx-dev-mcpVerify command exists:
which konnexx-dev-mcp # Mac/Linux where konnexx-dev-mcp # WindowsCheck Cursor settings:
Settings โ Features โ MCP
Verify
konnexx-devis listedCheck command path is correct
Restart Cursor completely (not just reload window)
Commands Not Loading
Check project type detection:
Verify project has proper markers (
composer.json,package.json, etc.)Check Cursor logs for detection messages
Verify command files exist:
npm list -g konnexx-dev-mcp # Check if commands/ directory exists in packageCheck remote source (if using remote commands):
Verify GitHub URL is accessible
Check
KONNEXX_MCP_USE_REMOTEis set to"true"
Wrong Project Type Detected
For Laravel projects: Ensure
composer.jsonexists and contains"laravel/framework"For Next.js projects: Ensure
package.jsonexists andnextis in dependenciesFor Architecture projects: Ensure project path contains "architecture" or add explicit marker
๐ Benefits vs .cursor Files
Aspect | .cursor Files (Old) | MCP Server (This) |
Installation | Copy to each project | Install once globally |
Updates | Copy-paste to all projects | Update once, team gets it |
Team Sync | Manual per project | Automatic (with remote) |
Maintenance | 4+ locations | 1 central location |
Versioning | Per-project Git | Centralized Git |
Consistency | Varies by project | Same everywhere |
๐ Documentation
๐ Getting Started
docs/GETTING_STARTED.md - Complete setup guide - Installation, configuration, and basic usage
docs/USAGE.md - How to use commands - Detailed guide on using commands in your projects
docs/QUICK_REFERENCE.md - Daily usage cheat sheet
๐ For Team Leads
docs/SETUP.md - Initial setup and publishing to npm
docs/PUBLISHING_WORKFLOW.md - Complete guide: How to update commands and publish new versions
๐ For Developers
docs/BEST_PRACTICES_REVIEW.md - Code review and best practices
docs/COMPREHENSIVE_ASSESSMENT.md - Complete codebase assessment
docs/COMMANDS_REVIEW.md - Commands directory structure review
docs/FIXES_APPLIED.md - Summary of fixes and improvements
๐ Reference
docs/README.md - Documentation index
CHANGELOG.md - Version history and changes
๐ What You Get
Once installed and configured:
โ One install, all projects - Works across all your Laravel, Next.js, Architecture, and Flutter projects
โ Auto-detection - No per-project configuration needed
โ Team consistency - Everyone uses the same commands
โ Easy updates - Update once, team gets it automatically
โ Version controlled - Commands stored as markdown in Git
โ MCP-enhanced - Commands use GitHub, Filesystem, Database, Context7 MCPs for better workflows
๐ฆ Package Information
Package Name:
konnexx-dev-mcpVersion: 1.1.0
GitHub: https://github.com/Konnexx-Software-Developers/konnexx-dev-mcp
License: MIT
Node.js: Requires 18.0.0 or higher
๐ฅ Team
Created for: DinDin & Konnexx Software Developers Team
Purpose: Centralize development workflow commands across all projects
Maintainer: DinDin @ Konnexx
๐ License
MIT - Konnexx Software Developers
Ready to get started? See docs/USAGE.md for complete usage instructions!
Available Tools
23 toolsarchitecture_reviewC
Review code for architectural compliance (DDD, Laravel patterns)
Inputs: no named parameters.
architecture_review_webB
Review code for architectural compliance (Next.js patterns)
Inputs: no named parameters.
clear_plansC
Execute workflow to automatically clear Cursor plan files from the project. Follows team standards for cleanup.
Inputs: no named parameters.
commit_prA
Execute complete commit and PR workflow: auto-detects project type, generates conventional commit messages, cleans up plan files, commits, pushes, and creates PR with proper formatting. Uses GitHub MCP for PR operations. ALWAYS use this instead of manual git commands to ensure team standards.
Inputs: no named parameters.
create_timeline_ganttC
Create timeline and Gantt chart from tickets and API endpoints
Inputs: no named parameters.
db_queryC
Execute database query workflow using Database MCP. Provides standardized query execution with proper error handling.
Inputs: query (required).
design_erdC
Design Entity-Relationship Diagram from requirements
Inputs: no named parameters.
docs_lookupC
Execute documentation lookup workflow using Context7 MCP. Provides up-to-date library documentation and code examples.
Inputs: query (required).
extract_requirementsD
Extract and structure requirements from documentation
Inputs: no named parameters.
generate_ticketsC
Generate development tickets in batches of 5 from API endpoints and timeline
Inputs: epic (required), phase (required).
generate_tickets_batchC
Generate multiple ticket batches for architecture projects
Inputs: epic (required), phases (required).
implement_featureB
Execute complete feature implementation workflow following team standards: plan โ approve โ implement โ review โ test. Uses MCP servers (GitHub, Database, Context7) for integrated workflow. ALWAYS use this for feature implementation to ensure consistency with team patterns (DDD, Laravel conventions).
Inputs: ticket (required), architecture_report.
implement_feature_mobileC
Implement a feature for Flutter mobile application
Inputs: ticket (required).
implement_feature_webB
Execute complete Next.js feature implementation workflow following team's 7-step process: Types โ Service โ Hooks โ Components โ Screens โ Routes. ALWAYS use this for Next.js features to ensure architectural compliance and consistency.
Inputs: ticket (required).
publish_packageA
Execute complete package publishing workflow: reviews changes, determines version bump, builds package, updates version, creates git commit and tag, pushes to GitHub, and publishes to npm. ALWAYS use this for publishing konnexx-dev-mcp to ensure proper versioning and tagging.
Inputs: no named parameters.
specify_api_endpointsC
Specify API endpoints from requirements and ERD
Inputs: no named parameters.
synthesize_documentationC
Orchestrate complete architecture workflow and synthesize all documentation
Inputs: no named parameters.
test_fixC
Run tests, identify failures, and fix them using parallel agents
Inputs: spec.
test_fix_incrementalB
Run tests incrementally, fixing failures as they occur (faster for large test suites)
Inputs: spec.
test_fix_incremental_webC
Run tests incrementally for Next.js application, fixing failures as they occur
Inputs: spec.
test_fix_webC
Run tests for Next.js application and fix failures
Inputs: spec.
test_packageA
Execute local package testing workflow: builds package, creates npm link, verifies MCP server startup, and validates command files. Use this to test the konnexx-dev-mcp package locally before publishing.
Inputs: no named parameters.
verify_mcp_serversB
Execute workflow to verify all MCP servers are working (Context7, GitHub, Filesystem, Database, Browser). Use this to test MCP connectivity and diagnose issues.
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelogโฆ
TDQS
Scored across 23 tools
Most tools are clearly distinct, but generate_tickets and generate_tickets_batch overlap significantly in purpose, both generating tickets. Additionally, synthesize_documentation orchestrates multiple individual workflow steps, which could lead to misselection when an agent only needs a single step.
Tool names follow a consistent verb_noun pattern (generate_tickets, design_erd, implement_feature), with platform-specific suffixes like _web and _mobile. Minor inconsistencies include abbreviations (db_query, docs_lookup) and the slightly awkward generate_tickets_batch.
At 23 tools, the server is on the heavy side of the ideal range. While the broad scope of development workflows justifies many tools, it borders on being overwhelming and could benefit from consolidation.
The tool surface covers the full development lifecycle from requirements and architecture through implementation, testing, PR creation, and package publishing. Some gaps exist (e.g., no explicit deployment or ticket update tools), but core workflows are well-covered.
Maintenance
Related MCP Connectors
A MCP server built for developers enabling Git based project management with project and personalโฆ
MCP server for your apps' tools and custom tools, plus hosted AI agents and approval-gated workflows
Official Duck Framework MCP server for AI-assisted development and project scaffolding.
Nifty's MCP server โ exposes tasks, projects, messages, and files as tools for AI agents.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceMCP server that equips AI agents with dev workflow tools including GitHub project management, conventional commits, visual regression testing, Jira/Confluence integration, and a persistent memory knowledge graph.14 npmMIT
- AlicenseCqualityBmaintenanceAn MCP server implementing Spec-Driven Development workflows for AI-agent CLIs and IDEs like Claude Code and Cursor, enabling spec-first development with automated workflow guidance and quality checks.1783 npm54MIT
- AlicenseNot gradedqualityDmaintenanceA modular MCP server integrating Jira and GitHub to automate developer workflows, enabling AI agents to manage issues, branches, commits, and pull requests directly from the IDE.MIT
- AlicenseAqualityDmaintenanceMCP server for developer workflow automation โ smart commits, secret scanning, PR descriptions, and more.5MIT