Skip to main content
Glama
samihalawa

Google Jules MCP

by samihalawa
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Related Servers

Alternatives to Google Jules MCP

No user-submitted related servers found.

    Related Servers

    • Jules API MCP

      GreyC
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that enables users to manage Google's Jules AI coding agent sessions directly from MCP-compatible clients. It supports creating sessions, approving execution plans, and interacting with session activity to streamline autonomous coding workflows.
      8 npm
      MIT

    • Jules MCP Server

      MikBin
      A
      license
      A
      quality
      C
      maintenance
      An MCP server for orchestrating Google Jules as a remote coding agent from a local coding agent, handling task decomposition, API dispatch, monitoring, intervention, code review, and PR merging.
      16
      7 npm
      MIT

    • Playwrightium

      analysta-ai
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server for browser automation that allows AI to perform web tasks using Playwright through direct commands, reusable YAML shortcuts, or custom scripts. It features secure environment variable management and guided automation creation to build robust, repeatable browser workflows.
      9 npm
      MIT

    • BrowserGenie MCP Server

      BrowserGenie
      A
      license
      B
      quality
      C
      maintenance
      An MCP server that provides AI models with full browser automation capabilities through Chrome. It enables navigation, interaction, screenshots, and complete DevTools access by bridging AI clients with a companion Chrome extension.
      99
      10 npm
      3
      Apache 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

    B3.2/5.0

    Scored across 13 tools

    Disambiguation4/5

    Most tools are clearly distinct (create/get/list/send/approve/resume/analyze), but jules_get_cookies and jules_set_cookies could be confused with session management or authentication setup, and jules_screenshot is a debugging aid that overlaps somewhat with jules_analyze_code in purpose. Overall, the core task lifecycle tools are unambiguous.

    Naming Consistency4/5

    The naming follows a consistent jules_verb_noun pattern (create_task, get_task, list_tasks, send_message, approve_plan, resume_task, analyze_code). Minor deviations: jules_bulk_create_tasks is a variant of create, and jules_setup_wizard, jules_get_cookies, jules_set_cookies, jules_screenshot are less verb-noun consistent but still readable.

    Tool Count4/5

    13 tools is within the well-scoped range, and each tool serves a distinct function in the Jules workflow. The count is slightly on the higher side due to session/cookie/screenshot utilities, but they are justifiable for a browser-automation-based MCP server.

    Completeness4/5

    The core task lifecycle is covered: create, get, list, send message, approve plan, resume, analyze. Missing operations like cancel/delete task or update task description are minor gaps. The authentication/session tools (setup_wizard, cookies) add completeness for the browser-based setup domain.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources