Skip to main content
Glama
franccesco

Bloomy MCP

by franccesco
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to Bloomy MCP

No user-submitted related servers found.

    Related Servers

    • mcp-graphql

      launchthatbrand
      A
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that enables LLMs to interact with GraphQL APIs by providing schema introspection and query execution capabilities.
      889 npm
      3
      MIT

    • Flow MCP Server

      lmcmz
      F
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that enables AI assistants to access Flow blockchain data and perform operations such as checking balances, resolving domains, executing scripts, and submitting transactions.
      1
      -

    • RL-MCP

      rlefko
      F
      license
      Not graded
      quality
      D
      maintenance
      A Model Context Protocol server that provides AI models with structured access to external data and services, acting as a bridge between AI assistants and applications, databases, and APIs in a standardized, secure way.
      2
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no overlap: execute_query performs operations, get_authenticated_user_id handles authentication, and get_mutation_details/get_query_details provide metadata. The two detail tools are differentiated by query vs mutation focus, preventing confusion.

    Naming Consistency5/5

    All tools follow a consistent verb_noun naming pattern with snake_case: execute_query, get_authenticated_user_id, get_mutation_details, get_query_details. The pattern is predictable and readable throughout the set.

    Tool Count5/5

    Four tools is well-scoped for a GraphQL-focused server: one for execution, one for authentication, and two for schema introspection. Each tool earns its place without bloat or thin coverage for the domain.

    Completeness4/5

    The surface covers core GraphQL workflows well: execution, authentication, and schema details for both queries and mutations. A minor gap is the lack of a tool for subscription details or general schema exploration beyond specific queries/mutations, but agents can work around this.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources