Skip to main content
Glama
VeyraX

VeyraX

Official
by VeyraX
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Related Servers

Alternatives to VeyraX

No user-submitted related servers found.

    Related Servers

    • Bernerspace by bernerspace

      Bernerspaceofficial

      bernerspace
      A
      license
      Not graded
      quality
      D
      maintenance
      A unified MCP server that provides OAuth-enabled integrations for multiple services through a single deployment. Currently supports Slack with 47 tools, with plans to expand to Gmail, Google Calendar, Notion, and 100+ other integrations.
      6
      MIT

    • Google-Workspace-MCP-Server

      giuseppe-coco
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server that seamlessly interacts with your Google Calendar, Gmail, Drive and so on.
      30
      MIT

    • 0nMCP

      0nork
      F
      license
      Not graded
      quality
      Not graded
      maintenance
      Universal AI API Orchestrator. 850 tools across 53 services under a single MCP interface. Connect Claude, GPT, or Gemini to Stripe, Slack, GitHub, LinkedIn, Cloudflare, Shopify, Twilio, and 46 more via natural language. $0.10/execution, no subscription. Patent Pending.
      126 npm
      5
      -

    • google-meta-ads-ga4-mcp

      irinabuht12-oss
      A
      license
      Not graded
      quality
      A
      maintenance
      Hosted remote MCP for Google Ads, Meta Ads (Facebook and Instagram), GA4 and Google Search Console. Connect Claude, ChatGPT, Cursor, Claude Code or Grok with a Google or Facebook login: audits, search terms, GAQL and Insights reports, keyword research, AI-referral traffic, and approved changes to budgets, bids and negatives. OAuth 2.1, no API keys, free.
      4,330
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    B3.4/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 roles, making misselection unlikely.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (get_flow, get_tools, tool_call) using snake_case throughout. This predictable naming scheme enhances readability and usability for agents.

    Tool Count3/5

    With only 3 tools, the server feels thin for its apparent scope of managing workflows and dynamic tools. While the tools cover core operations, the low count may limit functionality, such as lacking update or delete capabilities for workflows.

    Completeness3/5

    The tool set covers basic retrieval and execution (get_flow, get_tools, tool_call) but has notable gaps for a workflow management domain. Missing operations include creating, updating, or deleting workflows, which could hinder agent workflows that require full lifecycle management.

    Resources