mcp/veyrax repository overview

⁠VeyraX MCP Server

VeyraX MCP is the only connection you need to access all your tools in any MCP-compatible environment.

What is an MCP Server?⁠

⁠MCP Info

⁠Image Building Info

Attribute	Details
Dockerfile	https://github.com/VeyraX/veyrax-mcp/blob/4171ea88cc3a0e28599b68166eb54281470d622f/Dockerfile⁠
Commit	4171ea88cc3a0e28599b68166eb54281470d622f
Docker Image built by	Docker Inc.
Docker Scout Health Score
Verify Signature	COSIGN_REPOSITORY=mcp/signatures cosign verify mcp/veyrax --key https://raw.githubusercontent.com/docker/keyring/refs/heads/main/public/mcp/latest.pub
Licence

⁠Available Tools (3)

⁠Tools Details

⁠Tool: get_flow

"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."

⁠Tool: get_tools

"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: tool_call

"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."

⁠Use this MCP Server

{
  "mcpServers": {
    "veyrax": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "VEYRAX_API_KEY",
        "mcp/veyrax"
      ],
      "env": {
        "VEYRAX_API_KEY": "your-veyrax-api-key-here"
      }
    }
  }
}

Why is it safer to run MCP Servers with Docker?⁠