Skip to main content
Glama
jrb00013

mailnotmilk

by jrb00013
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to mailnotmilk

No user-submitted related servers found.

    Related Servers

    • Browserbeam MCP Server

      nyku
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables real browser automation as tools in Cursor, Claude Desktop, Windsurf, and any MCP-compatible client, allowing AI agents to interact with web pages through natural language.
      8 npm
      MIT

    • chromium-bridge

      dashi96
      A
      license
      A
      quality
      B
      maintenance
      MCP bridge between Chromium browsers (Arc, Vivaldi, Brave) and Claude Code. 18 browser automation tools (navigate, click, forms, screenshots, GIF recording, console, network) plus a popup chat panel powered by the Claude Agent SDK.
      18
      5
      MIT

    • Playwright MCP Server

      ryanatindago
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to control a browser through MCP tools for web automation tasks like navigation, typing, clicking, and screenshots. Deploys on Cloudflare Workers and works with Claude Desktop, GitHub Copilot, and Cloudflare AI Playground.
      -
    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

    C2.7/5.0

    Scored across 36 tools

    Disambiguation2/5

    Multiple tools have unclear boundaries: post_message vs chat_say vs browser_send_message all send messages but to different targets; check_inbox, list_history, and chat_history all retrieve messages but with different scopes. The many list/send variants make it hard for an agent to pick the right tool.

    Naming Consistency3/5

    There are consistent clusters (e.g., browser_* prefixed tools, verb_noun like check_inbox, read_message), but the overall set mixes conventions: chat_link and chat_history are noun phrases, mailbox_stats is noun_noun, and relay_tick is noun_verb. Still readable, but not uniform.

    Tool Count2/5

    With 36 tools, the server is overloaded, far beyond the typical well-scoped range. Even though it covers messaging, browser automation, and presence, the sheer number makes it unwieldy and suggests too many responsibilities for a single MCP server.

    Completeness3/5

    The messaging and presence lifecycle is fairly complete (send, read, reply, search, archive, react, status), but missing obvious operations like editing or deleting messages. Chat management is also thin (no leave/delete/rename), and browser automation is limited to AI pages. Notable gaps exist, but core workflows work.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources