Skip to main content
Glama
VeyraX MCP
by clarenous

VeyraX MCP

Single tool to control them all — VeyraX MCP is the only connection you need to access all your tools in any MCP-compatible environment.


Model Context Protocol (MCP)

Introduction

VeyraX MCP (Model Context Protocol) is an open protocol that allows you to provide custom tools to agentic LLMs. By connecting once to the VeyraX platform, you can use all tools you’ve already integrated with VeyraX in any MCP-compatible environment—such as Claude, Cursor, VS Code, or Windserf—without juggling multiple authentications.

Why Choose VeyraX?

  • Single Authentication: Connect once in VeyraX, then use your tools across all MCP clients without separate logins or credentials.

  • Instant Access to All Tools: Any tool you connect to VeyraX is immediately available in your favorite editor or AI assistant.

  • 5-Minute Setup: Connect VeyraX to any MCP client in under five minutes.


Related MCP server: MCPX MCP Gateway

Getting Started

  1. Sign up for VeyraX
    Create a free account at https://www.veyrax.com/register.

  2. Open the VeyraX Platform to Get Your API Key
    You can find your API key in your VeyraX dashboard.

    Tip: Look for the “API Key” section in your account settings.

  3. Choose Your Configuration
    Copy the complete configuration (including your API key) directly from the VeyraX platform.

  4. Select an MCP Client
    Decide which environment or editor you want to integrate with (e.g., Cursor, Claude, Windserf, VS Code).

  5. Follow the Setup Guide
    Either:

    • Use the automatic installation method (you’ll be prompted for your API key), OR

    • Manually paste the copied configuration into your MCP client’s settings.

That’s it! You’ll now have instant access to every tool you’ve linked to VeyraX in all your favorite editor and AI assistant environments.


Supported MCP Clients

  • Cursor
    Add VeyraX MCP to Cursor IDE in minutes.

  • Claude
    Use all your VeyraX-connected tools directly in Claude.

  • Windsurf
    Integrate with the Windserf IDE for a seamless coding experience.

  • VS Code
    Connect VeyraX MCP to VSCode IDE via Cline.


Have Questions?

If you have any questions, check out our documentation or contact support.

Enjoy a unified, hassle-free approach to using all your favorite tools anywhere, all thanks to VeyraX MCP!


Happy coding!

— Team VeyraX


This README is a brief starter guide. For detailed instructions and troubleshooting, please visit the official VeyraX docs.

Available Tools

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

Inputs: flowId (required).

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

Inputs: question (required), tool (required).

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

Inputs: tool (required), method (required), parameters, question.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.7/5.0

    Scored across 3 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      A central hub that aggregates multiple MCP resource servers into a single unified interface, enabling users to access tools and capabilities from multiple backend servers through one connection point.
      202
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      MCPX is a remote-first MCP aggregator that enables zero-code integration, unified access, and dynamic routing across multiple MCP servers. It offers tool-level access controls, usage visibility, and customization to streamline and secure agentic workflows.
      510
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Centralized authentication, authorization, and audit for MCP tools. One server governs every downstream MCP your organization uses.
      3
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables clients to access multiple backend MCP servers through a single endpoint, with OAuth 2.1 authorization, namespaced tools, and secure credential management.
      2
      AGPL 3.0