engmanager-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| ENGMANAGER_MCP_LOG_LEVEL | No | Logging level (DEBUG, INFO, WARNING, ERROR) | |
| ENGMANAGER_MCP_TRANSPORT | No | Transport mode (stdio or http) | |
| ENGMANAGER_PROCEDURES_DIR | No | Custom procedures directory | |
| ENGMANAGER_DEFAULT_PROJECT | No | Default project name |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_next_stepA | Get the next step in the workflow Retrieves the next step in the development workflow for the specified project. If current_step is provided, returns the step immediately following it. If current_step is not provided, returns step 1 (start of workflow). Args: project: Project name (uses default if not specified) current_step: Current step number (optional, defaults to 0 to get step 1) Returns: Formatted next step instructions Examples: get_next_step(project="trowel") get_next_step(project="trowel", current_step=3) |
| get_workflow_sectionA | Get a specific section from the workflow Retrieves a named section from the project's workflow procedure. Useful for jumping to specific parts of the workflow or getting reference information. Args: section: Section title to retrieve project: Project name (uses default if not specified) Returns: Section content Examples: get_workflow_section(section="Error Recovery Protocols", project="trowel") get_workflow_section(section="Quality Gates") |
| list_workflow_stepsA | List all steps in the workflow Provides an overview of all numbered steps in the project's workflow. Args: project: Project name (uses default if not specified) Returns: List of all workflow steps Examples: list_workflow_steps(project="trowel") list_workflow_steps() |
| list_available_projectsA | List all configured projects Shows all projects that have configuration files available. Returns: List of available project names Examples: list_available_projects() |
| get_project_infoA | Get information about a specific project Shows configuration and available procedures for a project. Args: project: Project name Returns: Project information including variables and procedure file Examples: get_project_info(project="trowel") |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| get_templates | Get information about available template variables Returns: Documentation of template variable syntax and examples |
| list_projects | List all available projects Returns: List of configured projects |
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/scarr7981/engmanager-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server