workflow-generator
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| generate_workflowA | Scan a project directory and generate WORKFLOW.html — a visual system workflow showing all components, their communication paths, concurrency model, concurrent request capacity, and bottleneck analysis. Works with Python (FastAPI, Flask, Django), Node.js (Express, Nest.js), Go, and mixed projects. Detects: API frameworks, gateways, LLM providers, vector stores, databases, queues, rate limits, async primitives, and worker counts. |
| analyze_workflowA | Scan a project and return the workflow analysis as structured JSON (no file written). Returns: framework, workers, capacity estimates, detected components (LLM, storage, queues, external sources), concurrency primitives (semaphores, rate limits), and bottleneck ranking. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- 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/askuma/workflow-generator'
If you have feedback or need assistance with the MCP directory API, please join our Discord server