Skip to main content
Glama
Fibery-inc

Fibery MCP Server

Official
by Fibery-inc

Related Servers

Alternatives to Fibery MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      An MCP server that lets LLMs interact with your Clockify workspace for time-tracking automation and reporting, enabling natural language logging of time entries, querying entries, and generating reports.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      The Fabric-Analytics-MCP server enables AI agents to interact directly with Microsoft Fabric using natural language. It transforms complex data engineering tasks—such as workspace management, data exploration, and job execution—into intuitive, conversational workflows for LLMs like Claude or GitHub
      12 npm
      110
      MIT
    • A
      license
      Not graded
      quality
      F
      maintenance
      A local MCP server that integrates with Claude Desktop, enabling RAG capabilities to provide Claude with up-to-date private information from custom LlamaCloud indices.
      225
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      A dead simple MCP server for exposing your app functions to AI agents like Claude Desktop.
      16 npm
      6
      MIT

    TDQS

    B3.4/5.0

    Scored across 7 tools

    Disambiguation3/5

    Most tools have distinct purposes (create, list, describe, query, update), but create_entity and create_entities_batch have significant overlap—both create entities, differing only in batch capability. The current_date tool stands out as a utility that doesn't clearly align with the Fibery domain, potentially causing confusion about its role in the set.

    Naming Consistency4/5

    The naming follows a consistent verb_noun pattern (e.g., create_entity, list_databases, query_database) with clear, descriptive names. The only minor deviation is current_date, which uses a noun_noun pattern instead of a verb, slightly breaking the convention but remaining readable.

    Tool Count4/5

    With 7 tools, the count is reasonable for a Fibery integration, covering core operations like creation, listing, querying, and updating. It's slightly lean but functional, as it includes essential CRUD-like actions and schema exploration tools, though it might benefit from a delete tool for full lifecycle coverage.

    Completeness3/5

    The toolset covers key operations for interacting with Fibery databases, including creation, querying, and updating, with tools for schema exploration. However, there are notable gaps: no delete_entity tool limits full CRUD coverage, and the current_date utility feels out of place without clear integration into the domain, potentially leaving agents unable to perform complete entity management workflows.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive