apache-hop-mcp
by michaaels
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HOP_RUN | No | Path to hop-run.sh or hop-run.bat for local execution. | |
| HOP_HOME | Yes | Path to the unpacked Apache Hop installation. | |
| HOP_MCP_JAVA | No | Custom path to the JDK java binary. | |
| HOP_LOG_LEVEL | No | Hop log level (e.g. BASIC). | |
| HOP_RUN_CONFIG | No | Hop run configuration name (e.g. local). | |
| HOP_PROJECT_NAME | Yes | Name of the Apache Hop project. | |
| HOP_PROJECT_ROOT | Yes | Path to the Apache Hop project root directory. | |
| HOP_MCP_BRIDGE_JAR | No | Custom path to the apache-hop-mcp-bridge JAR. Normally unnecessary because the wheel contains the bridge. | |
| HOP_MCP_ALLOW_WRITE | No | Whether to allow write operations. Deny-by-default is recommended. | false |
| HOP_MCP_NATIVE_MODE | No | Engine mode for the native bridge: auto, native, or python. Auto is recommended. | auto |
| HOP_MCP_ALLOW_EXECUTE | No | Whether to allow execute operations. Deny-by-default is recommended. | false |
| HOP_PLUGIN_BASE_FOLDERS | No | Comma-separated list of additional plugin base folders. | |
| HOP_MCP_NATIVE_TIMEOUT_SECONDS | No | Timeout in seconds for native bridge operations. |
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
No tools | |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
This server cannot be deployed
Maintenance
ActivityMaintained
ResponsivenessNo issues