Skip to main content
Glama

Related Servers

Alternatives to monograph-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to work with estimates, quotes, job schedules, variations, and progress claims in a user's signed-in Buildxact account, with write actions requiring approval by default.
      Elastic 2.0
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to operate a user's signed-in Joist account, creating estimates, sending invoices, managing clients, and reviewing overdue payments through natural language without a Joist API key. It supports hosted MCP access plus a local stdio server for clients that require it.
      7
      Elastic 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Lets any MCP-speaking AI agent drive your everyday Chrome browser, opening pages, reading them, clicking, typing, taking screenshots, and inspecting DevTools console, network, storage and performance data with your existing sign-ins. Risky actions like submitting or paying require your explicit approval, and agents are confined to their own tab group with secrets hidden.
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to drive Chrome through MCP tools for navigating pages, taking token-efficient snapshots and diffs, finding and acting on elements, and capturing screenshots. Sensitive actions such as submitting forms, downloading or uploading files, and running JavaScript require human approval through a system dialog.
      MIT

    TDQS

    A3.7/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool has a clearly distinct role: guide, readiness check, opening a session, reading the page, clicking, typing, and closing. The boundaries between setup, interaction, and teardown are obvious, with almost no risk of tool misselection.

    Naming Consistency5/5

    All tools share the same monograph_ prefix and use short lower_snake_case names. The pattern is predictable throughout, with only guide/status being nouns and the rest actions, which is still highly consistent.

    Tool Count5/5

    Seven tools are well-scoped for a browser automation wrapper: just enough to cover setup, page interaction, and cleanup. No tool feels redundant or out of place.

    Completeness4/5

    The set covers the core browser lifecycle: guide, status, open, read, click, type, and close. Minor gaps exist for general browser operations like scrolling, selecting dropdown options, or explicit navigation, but agents can likely work around them.