Smart Agent Workflow MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_worktreeB | Creates an ephemeral git worktree for isolated feature development |
| worktree_statusA | Lists all active worktrees with their metadata |
| cleanup_worktreeA | Merges worktree to main and removes it. REQUIRES tests and build to pass first! Run run_e2e_tests and verify_build before calling this. Use force=true to bypass (NOT recommended). |
| abort_worktreeA | Aborts worktree without merging. Use when feature is cancelled. |
| run_e2e_testsA | Runs E2E tests with Playwright. Tests MUST pass before merge. Supports retries and custom test paths. |
| verify_buildA | Runs npm build and validates the output. Build MUST succeed before merge. |
| generate_test_templateA | Generates a Playwright E2E test template for a feature. Every feature MUST have tests before merge. |
| get_test_resultsA | Gets the latest test and build results from a worktree. Shows if the testing gate has been passed. |
| start_featureA | Starts a new feature with full workflow: creates worktree, sets up environment, initializes tracking. This is the recommended way to begin any development work. |
| complete_featureA | Completes a feature: runs E2E tests, verifies build, merges to main, cleans up worktree. BLOCKS if tests or build fail. This is the safe way to merge - quality gates cannot be bypassed. |
| rollback_featureA | Rolls back a failed or unwanted feature: aborts worktree, cleans up branch, records reason. Use this when you need to abandon a feature without merging. |
| get_workflow_statusC | Gets the current status of all active workflows, including phase, steps, and progress. |
| update_documentationA | Updates project documentation (CLAUDE.md, README.md) with information from the current workflow. Can auto-detect sections or target specific ones. Useful for keeping docs in sync with development. |
| generate_completion_reportA | Generates a detailed markdown report for a completed feature workflow. Includes test results, build status, timing, and git changes summary. Reports are saved to .smart-agent-workflow/reports/ |
| sync_changelogA | Syncs CHANGELOG.md with workflow information. Follows Keep a Changelog format. Automatically detects version from package.json and categorizes changes based on feature type. |
| save_contextA | Save the current workflow context to memory. Captures decisions, learnings, and file changes for future sessions. Use this to persist important context before completing or rolling back a feature. |
| restore_contextA | Restore context from a previous workflow. Retrieves decisions, learnings, files modified, and related memories. Use this to resume work on a feature or learn from past implementations. |
| get_memoryA | Query the knowledge graph for relevant memories. Search by content, filter by type (decision, learning, error, etc.), tags, workflow, or file path. Returns sorted by importance and recency. |
| checkpoint_contextA | Save the current workflow state and reset health score. Creates a checkpoint before context is lost to compaction. Use when health is critical or before long operations. Returns health before/after and entries saved. |
| get_context_healthA | Get current context health metrics: health score, operations count, estimated tokens, session duration, and whether checkpoint is recommended. Use this to monitor context usage and anticipate compaction. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Worktree Status | Current status of all active smart-agent worktrees |
| Latest Test Results | Latest test and build results from all worktrees. Shows testing gate status. |
| Current Workflow | Current active workflow with phase, steps, and progress |
| Project Documentation | Information about project documentation: available files, sections, and improvement suggestions. |
| Knowledge Graph | Overview of accumulated knowledge: decisions, learnings, errors, and workflow contexts |
| Statusline Workflow | Workflow progress and context health for statusline display |
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/vjrivmon/smart-agent-workflow-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server