sdlc-workflow-mcp
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., "@sdlc-workflow-mcpshow my pending workflow tasks"
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.
sdlc-workflow-mcp
A standalone stdio Model Context Protocol server that exposes a bounded, fictional-data slice of the SDLC workflow tools for local Copilot use.
Provenance: extracted from
Tingsum26/sdlc-agent-platformat theseven-repo-split-baselinetag (commitbf48e15), source pathapps/workflow-mcp. This repository is one slice of the seven-repository split described in the platform BOM (docs/platform-bom.yaml).
What this is
A TypeScript MCP server (
stdiotransport) that proxies a bounded set of workflow tools to a local Workflow Service over HTTP.All fixtures are fictional (
example.invalid,REPO_A,DEMO-123,EPIC-DEMO-1, fictional identities). There is no model client, no credentials, and no real company data in this slice.
What this is not (registered gap)
The full approved tool catalog in the platform BOM is larger than this slice. This repository
registers only the subset implemented in the apps/workflow-mcp vertical slice at split time
(workflow tasks, internal-readiness, epic/ticket/repo-task, change-request, and journey tools).
Remaining catalog tools are tracked in the originating platform BOM and its migration map, not here.
Prerequisites
Node.js >= 20.19.0
pnpm
Build and test
pnpm install
pnpm build
pnpm testStarting the stdio server
The server requires a Workflow Service URL and speaks MCP over stdio:
pnpm install
pnpm build
WORKFLOW_SERVICE_URL=http://127.0.0.1:8080 node dist/index.jsEnvironment variables:
Variable | Required | Description |
| yes | Base URL of the local Workflow Service (e.g. |
| no | Demo identity; allowed only when the service host is loopback. |
On startup failure or missing configuration, the server writes a structured JSON diagnostic to
stderr and exits with code 2.
Layout
src/— MCP server, API client, diagnostics, and tool registration.test/— vitest suite covering tool discovery, correlation IDs, audit visibility, safe error mapping, cancellation, and stderr redaction.
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 Connectors
Workflow diagnostics, capability routing, and x402 settlement for MCP-compatible agents.
An MCP server that let you interact with Cycloid.io Internal Development Portal and Platform
MCP server for AI agents to plan, verify, and deploy Cloudflare-native apps.
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/Tingsum26/sdlc-workflow-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server