VeyraX MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VEYRAX_API_KEY | Yes | Your VeyraX API key from your account settings |
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 |
|---|---|
| get_toolsB | "Use this tool to retrieve a list of available tools from the Veyrax API. This will return dynamic tools that user has access to. You can use this tool to get the list of tools, method names and parameters, and then use tool_call tool to call the tool with the provided parameters. This method also returns all flows with name and id that user has access to (if any). " |
| tool_callB | "Use this tool to execute a specific method of another tool with the provided parameters based on get-tools tool response. You need to specify the tool name, method name, and any required parameters for that method." |
| get_flowB | "Use this tool to retrieve a specific workflow by its ID. Workflow is sequence of steps that are executed in order to get some result. Flow comes with description, steps and input schema of all methods to call. You can call this tool once you have a flowId which usually you can get from: user directly OR using get-tools method." |
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 3 tools
Each tool has a clearly distinct purpose with no overlap: get_flow retrieves a specific workflow, get_tools lists available tools and flows, and tool_call executes a method from another tool. The descriptions explicitly differentiate their functions, making misselection unlikely.
All tool names follow a consistent snake_case pattern with clear verb_noun structures: get_flow, get_tools, and tool_call. This uniformity enhances readability and predictability across the set.
With 3 tools, this server is well-scoped for its purpose of managing workflows and dynamic tools. Each tool earns its place by covering essential operations: retrieving workflows, listing tools, and executing tool methods, without being overly sparse or bloated.
The tool set provides complete coverage for core workflows: retrieving tools and flows, and executing methods. A minor gap exists in lifecycle management (e.g., creating or updating flows), but agents can work around this given the dynamic nature of the tools, and the surface supports the stated purpose effectively.