OneTech MCP Server
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
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| onetech_extract_moduleA | Extract domain model, pages, microflows, and enumerations from a Mendix module using mx.exe. Returns JSON files with complete module structure. |
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 1 tool
With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool has a clear, distinct purpose focused on extracting module structure from Mendix.
The naming follows a consistent verb_noun pattern (onetech_extract_module), and with only one tool, there is no inconsistency to evaluate. The name clearly describes the action and target.
A single tool is too few for most server purposes, as it severely limits functionality and suggests an incomplete or overly narrow scope. While the tool itself might be useful, the set lacks breadth for typical MCP server operations.
The server appears to target Mendix module extraction, but with only one tool, there are significant gaps. There is no coverage for creating, updating, deleting, or querying modules, making the surface incomplete for any robust workflow in this domain.