GIMS Automation MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GIMS_URL | Yes | URL GIMS сервера | |
| GIMS_VERIFY_SSL | No | Проверка SSL сертификата (по умолчанию: true) | true |
| GIMS_ACCESS_TOKEN | Yes | JWT токен доступа | |
| GIMS_REFRESH_TOKEN | Yes | JWT токен обновления | |
| GIMS_LOG_STREAM_TIMEOUT | No | Таймаут для SSE-потока логов в секундах (по умолчанию: 60) | 60 |
| GIMS_MAX_RESPONSE_SIZE_KB | No | Лимит размера ответа в КБ (по умолчанию: 10) | 10 |
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_script_foldersA | List all script folders with their hierarchy paths |
| create_script_folderB | Create a new script folder |
| update_script_folderC | Update an existing script folder |
| delete_script_folderC | Delete a script folder |
| list_scriptsA | List all scripts with their folder paths |
| get_scriptA | Get script metadata by ID. Code is filtered by default - use get_script_code to retrieve code. |
| get_script_codeA | Get the full code of a script by ID. Use this when you need to read or analyze the script code. |
| create_scriptC | Create a new script |
| update_scriptC | Update an existing script |
| delete_scriptC | Delete a script |
| search_scriptsA | Search scripts by name and/or code content. Default searches by name only. |
| list_datasource_type_foldersA | List all datasource type folders with their hierarchy paths |
| create_datasource_type_folderB | Create a new datasource type folder |
| update_datasource_type_folderC | Update a datasource type folder |
| delete_datasource_type_folderC | Delete a datasource type folder |
| list_datasource_typesA | List all datasource types |
| get_datasource_typeA | Get a datasource type. Use include_properties=false and include_methods=false to get only basic type info (useful when full response is too large) |
| create_datasource_typeC | Create a new datasource type |
| update_datasource_typeC | Update a datasource type |
| delete_datasource_typeB | Delete a datasource type |
| list_datasource_type_propertiesB | List all properties of a datasource type |
| create_datasource_type_propertyA | Create a new property for a datasource type. Property is accessed in method code via self.property_label |
| update_datasource_type_propertyC | Update a datasource type property |
| delete_datasource_type_propertyB | Delete a datasource type property |
| list_datasource_type_methodsA | List all methods of a datasource type (without code, use get_datasource_type_method for full code) |
| get_datasource_type_methodA | Get method metadata and parameters. Code is filtered - use get_datasource_type_method_code to retrieve code. |
| get_datasource_type_method_codeA | Get the full code of a datasource type method. Use this when you need to read or analyze the method code. |
| create_datasource_type_methodB | Create a new method for a datasource type |
| update_datasource_type_methodB | Update a datasource type method (including its code) |
| delete_datasource_type_methodC | Delete a datasource type method |
| list_method_parametersA | List all parameters of a method |
| create_method_parameterA | Create input or output parameter for a datasource type method. Input parameters (input_type=true) are passed when calling the method. Output parameters (input_type=false) are returned as dict from the method. |
| update_method_parameterD | Update a method parameter |
| delete_method_parameterB | Delete a method parameter |
| search_datasource_typesA | Search datasource types by name and/or method code. Default searches by name only. |
| list_activator_type_foldersA | List all activator type folders with their hierarchy paths |
| create_activator_type_folderC | Create a new activator type folder |
| update_activator_type_folderD | Update an activator type folder |
| delete_activator_type_folderC | Delete an activator type folder |
| list_activator_typesA | List all activator types |
| get_activator_typeA | Get activator type metadata. Code is filtered by default - use get_activator_type_code to retrieve code. |
| get_activator_type_codeA | Get the full code of an activator type. Use this when you need to read or analyze the activator code. |
| create_activator_typeC | Create a new activator type |
| update_activator_typeB | Update an activator type (including its code) |
| delete_activator_typeB | Delete an activator type |
| list_activator_type_propertiesB | List all properties of an activator type |
| create_activator_type_propertyA | Create a new property for an activator type. Property is accessed in activator code directly by label name (NOT through self). |
| update_activator_type_propertyC | Update an activator type property |
| delete_activator_type_propertyB | Delete an activator type property |
| search_activator_typesA | Search activator types by name and/or code. Default searches by name only. |
| list_value_typesA | List all available value types for properties and parameters. Use this to get value_type_id when creating properties. |
| list_property_sectionsA | List all available property sections. Use this to get section_name_id when creating properties. |
| get_script_execution_logA | Get script execution log via SSE stream. Waits for end marker or timeout. Use this to collect script output after manual script execution in GIMS. |
| export_scriptA | Export a script from GIMS to Git format (meta.yaml + code.py) |
| import_scriptA | Import a script to GIMS from Git format. Validates Python syntax before import. |
| export_datasource_typeB | Export a datasource type with all properties and methods |
| import_datasource_typeB | Import a datasource type from Git format |
| export_activator_typeB | Export an activator type with properties and code |
| import_activator_typeC | Import an activator type from Git format |
| validate_python_codeB | Validate Python code syntax using ast.parse() |
| compare_with_gitA | Compare a GIMS component with its Git version (by updated_at) |
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
- 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/gelarm/gims-automation-mcp-server'
If you have feedback or need assistance with the MCP directory API, please join our Discord server