ScriptFlow MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SCRIPTFLOW_TIMEOUT | No | Execution timeout in ms | 30000 |
| SCRIPTFLOW_SCRIPTS_DIR | No | Scripts directory | /tmp/scriptflow-mcp/scripts |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| script_addB | Add a new script to the repository |
| script_listC | List and discover available scripts |
| script_runC | Execute a script by name |
| script_editB | Edit an existing script |
| script_rmB | Remove a script from the repository |
| script_getB | Get detailed information about a specific script |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 6 tools
Each tool maps to a distinct action on scripts: add, list, run, edit, rm, and get. There is no overlap or ambiguity between them.
All tools follow the consistent pattern 'script_' followed by a clear verb (add, list, run, edit, rm, get). This creates a predictable and intuitive naming scheme.
With 6 tools, the set is well-scoped for managing scripts. Each tool serves a necessary function without unnecessary bloat or gaps.
The toolset covers the full lifecycle of scripts: create (add), read (get, list), update (edit), delete (rm), and execution (run). No obvious missing operations for the stated domain.