MCP Workflow Engine
Click on "Install 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., "@MCP Workflow Enginecheck the impact of modifying src/services/user.ts"
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.
MCP Workflow Engine
MCP server that provides AI coding agents with dependency analysis, impact detection, and build verification tools.
Tools Provided
Tool | Description |
| Find all files affected by changes to a file |
| Aggregate impact across a diff or git changeset |
| List what a file imports |
| Get dependency graph statistics and circular deps |
| Run build and return pass/fail with errors |
| Run TypeScript type checking |
| Run linter |
| Suggest test files impacted by a change |
| Run tests (auto-detected if not provided) |
| Run only a provided list of tests (uses |
| Highlight potential API/contract impacts |
| Generate verification checklist for a file type |
| Generate checklists for multiple files |
| Clear cached dependency graph |
Related MCP server: OpenCodeHub MCP Server
Auto-Detection Behavior
Dependency scanning defaults to
src, but if it doesn't exist the server auto-detects common source roots (e.g.lib,app,apps,packages,services) and includes common test dirs (test,tests,__tests__,spec,specs) when present.You can override scanning with
scan_dirs,project_root, andignore_patterns.Build and test commands auto-detect common ecosystems (Node, Gradle, Maven, .NET, Go, Rust, Python, Make). You can always pass an explicit
command.
Installation
cd mcp-workflow
npm install
npm run buildConfiguration
Claude Code
Add to ~/.claude/settings.json:
{
"mcpServers": {
"workflow-engine": {
"command": "node",
"args": ["C:/path/to/mcp-workflow/dist/server.js"]
}
}
}Codex CLI
Add to ~/.codex/config.toml:
[mcp_servers.workflow-engine]
command = "node"
args = ["C:/path/to/mcp-workflow/dist/server.js"]Repo Config (.workflow-engine.json)
Place this in the repo being analyzed (the project_root). It overrides auto-detection.
Notes:
ignorePatternsare regular expressions matched against normalized paths (e.g.src/foo/bar.ts).testCommandsupports{tests}placeholder for targeted runs.dependencyCruiserOptionsis passed through to dependency-cruiser (advanced use).contractDirsscopes where contract files are discovered (defaults to common docs/spec folders).
{
"scanDirs": ["src", "packages"],
"testDirs": ["tests", "__tests__"],
"ignorePatterns": ["\\.generated\\.", "^dist/"],
"contractDirs": ["docs", "spec", "openapi"],
"buildCommand": "pnpm build",
"testCommand": "pnpm test -- {tests}",
"dependencyCruiserOptions": {
"tsConfig": "tsconfig.json"
}
}Usage Examples
Once configured, the agent can call these tools:
Before implementing a change
Agent: I need to modify src/services/user.ts. Let me check the impact.
[Calls get_impact(file="src/services/user.ts", project_root="C:/path/to/project")]
Result:
{
"file": "src/services/user.ts",
"directDependents": ["src/controllers/auth.ts", "src/controllers/admin.ts"],
"transitiveDependents": ["src/routes/api.ts"],
"associatedTests": ["src/services/__tests__/user.test.ts"],
"totalImpacted": 3
}Get verification checklist
Agent: What should I verify for this change?
[Calls chain_effect_checklist(file="src/services/user.ts")]
Result:
{
"file": "src/services/user.ts",
"fileType": "Service/Domain",
"checklist": [
{"category": "Controllers", "check": "Verify all calling controllers handle new behavior"},
{"category": "Return Types", "check": "Check if return type changes affect callers"},
...
]
}After implementing
Agent: Let me verify the build passes.
[Calls verify_build()]
Result:
{
"success": true,
"output": "Build completed successfully",
"errors": [],
"duration": 3420
}Diff-aware impact
Agent: What will this diff impact?
[Calls get_impact_from_diff(cwd="C:/path/to/project")]Relevant tests + execution
Agent: Which tests should I run?
[Calls get_relevant_tests(files=["src/services/user.ts"], project_root="C:/path/to/project")]
Agent: Run those tests.
[Calls run_relevant_tests(tests=["src/services/__tests__/user.test.ts"], command="pnpm test -- {tests}")]Contract impact
Agent: Any contract updates needed?
[Calls get_contract_impact(files=["src/controllers/user.ts"], project_root="C:/path/to/project")]Workflow Integration
Pair with an AGENTS.md file in your repo:
## Required Workflow
### Step 1: Impact Analysis
Before implementing, use `get_impact` to identify all affected files.
### Step 2: Chain-Effect Checklist
Use `chain_effect_checklist` to get verification items for the file type.
### Step 3: Implementation
Make changes across all affected layers.
### Step 4: Build Verification
Use `verify_build` - task is NOT complete unless this returns success.Development
npm run dev # Watch mode
npm run build # Build once
npm start # Run serverLicense
MIT
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Servers
Alicense-qualityCmaintenanceGives AI agents instant access to software architecture, dependencies, and impact analysis through pre-computed sgraph models, replacing dozens of grep/read cycles with a single tool call.Last updated3MIT- Alicense-qualityCmaintenanceProvides code intelligence for AI coding agents by indexing repositories into a hybrid knowledge graph, enabling agents to query dependencies, impact, and context through 28 MCP tools.Last updated2Apache 2.0
- Alicense-qualityCmaintenanceProvides semantic code search and code insights via a knowledge graph, enabling AI to understand, navigate, and modify complex projects with deep dependency and architecture analysis.Last updatedMIT
- Alicense-qualityCmaintenanceEnables AI agents to map cross-repository dependencies, detect breaking changes in API contracts, and assess impact across services.Last updatedMIT
Related MCP Connectors
AI Agent with Architectural Memory. Impact analysis (free), tests and code from the graph (pro).
Give your AI agent a persistent map of your project's structure, dependencies, and bugs.
Package intelligence for AI agents across npm, PyPI, crates.io and deps.dev. No API keys.
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/rubinownz111/agent-accuracy'
If you have feedback or need assistance with the MCP directory API, please join our Discord server