Skip to main content
Glama
Sign In
Bloom MCP

Bloom MCP

by cotlet-connect
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to Bloom MCP

No user-submitted related servers found.

    Related Servers

    • Booksy MCP Server

      cotlet-connect
      A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to work within a user's signed-in business account to read and change bookings and client lists, including booking, rescheduling, finding open slots, and following up with clients.
      7
      Elastic 2.0

    • fresha-mcp

      cotlet-connect
      A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to manage appointments, reschedule bookings, look up clients, and add client notes in a user's signed-in business account without requiring an API key.
      7
      Elastic 2.0

    • glossgenius-mcp

      cotlet-connect
      A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to work in a user's signed-in GlossGenius account, allowing natural-language booking, rescheduling, schedule queries, and client follow-ups without requiring a GlossGenius API key.
      7
      Elastic 2.0
    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

    A3.6/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool has a clearly distinct role: guide, status check, browser open/close, and page read/click/type. No two tools overlap in purpose, so an agent can easily select the right one.

    Naming Consistency4/5

    All tools share the bloom_ prefix and snake_case, but most are verbs (open, read, click, type, close) while guide and status are noun-based. The pattern is still predictable and readable.

    Tool Count5/5

    Seven tools are well-scoped for a browser-automation server: one setup guide, one readiness check, and five core session/page operations. Each tool earns its place.

    Completeness4/5

    The surface covers session lifecycle and basic page interaction (open, read, click, type, close), which is sufficient for core UI workflows. Minor gaps like scroll, select, or keyboard shortcuts exist but agents can work around them.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources