Skip to main content
Glama
AlexandreCalvet

Ogury MCP Server

Related Servers

Alternatives to Ogury MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      An MCP server that integrates Kagi search capabilities with Claude AI, enabling Claude to perform real-time web searches when answering questions that require up-to-date information.
      2
      527
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that allows accessing and managing ledger files through Claude by providing account listing, balance checking, and transaction register viewing capabilities.
      4
      GPL 3.0
    • F
      license
      Not graded
      quality
      D
      maintenance
      A production-ready MCP server ecosystem providing Claude AI with 150+ specialized tools across enhanced memory, data analytics, security, design, and infrastructure domains with PostgreSQL, Redis, Qdrant, and Docker orchestration.
      -
    • A
      license
      C
      quality
      D
      maintenance
      An MCP server that provides seamless integration with Claude Desktop for querying and managing timeseries data in GigAPI Timeseries Lake.
      7
      6
      Apache 2.0
    • A
      license
      B
      quality
      D
      maintenance
      MCP server that allows Claude AI to interact directly with MySQL databases, enabling query execution and table information retrieval through natural language.
      1
      2 npm
      4
      MIT

    TDQS

    C2.7/5.0

    Scored across 2 tools

    Disambiguation2/5

    The two tools have overlapping purposes, as both retrieve campaign performance data, which could cause confusion for an agent. While 'get_campaign_details' targets a specific campaign by ID and 'get_campaigns_report' offers flexible filtering, the descriptions do not clearly differentiate their use cases, leading to potential misselection.

    Naming Consistency5/5

    The tool names follow a consistent verb_noun pattern with 'get_campaign_details' and 'get_campaigns_report', both using snake_case and starting with 'get'. This predictability makes it easy for agents to understand the naming convention.

    Tool Count2/5

    With only 2 tools, the server feels thin and under-scoped for a campaign management domain, as it lacks essential operations like creating, updating, or deleting campaigns. This limited set may hinder agent workflows and suggests an incomplete implementation.

    Completeness2/5

    The tool surface is severely incomplete for campaign management, covering only read operations (details and reports) without any create, update, or delete capabilities. This creates significant gaps that will likely cause agent failures in handling full campaign lifecycles.