Skip to main content
Glama
georgeracu

google-jules-mcp-server

by georgeracu
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to google-jules-mcp-server

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

    • jules-dispatch

      Yuuqq
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server for batch-dispatching coding tasks to Google Jules in parallel, with YAML task definitions, plan approval, and optional LLM-based task planning. Integrates with Claude Code and OpenAI Codex CLI as a tool.
      21 npm
      4
      MIT

    • Google Jules MCP

      samihalawa
      A
      license
      B
      quality
      D
      maintenance
      An MCP server for automating Google Jules that enables seamless integration for task creation, code analysis, and AI-powered development workflows. It supports multiple session modes including Browserbase and cookie-based authentication for both local and cloud environments.
      13
      27 npm
      14
      MIT
    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.7/5.0

    Scored across 20 tools

    Disambiguation4/5

    Most tools target distinct resources and actions, but the monitoring tools (get_status, list_activities, get_activity, wait_for_session) have overlapping purposes and could cause some selection hesitation. Descriptions generally clarify the differences, so ambiguity is limited to a few related tools.

    Naming Consistency5/5

    All tools share a consistent jules_ prefix and follow a clear verb_noun pattern such as create_session, list_sessions, archive_session, and get_activity. This makes the API predictable and easy to navigate.

    Tool Count4/5

    With 20 tools, the server is on the higher end of the ideal range, but the count is justified by the breadth of session management, source management, recurring schedules, and activity monitoring. A few tools like jules_get_activity and jules_list_stuck_sessions are somewhat specialized but still serve distinct workflows.

    Completeness4/5

    The server covers the main Jules lifecycle well: create, list, monitor, interact, output retrieval, archive, delete, bulk operations, and recurring schedules. The most notable gap is the lack of an explicit cancel/terminate action for a running session, though send_message may serve as a partial workaround.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive

    Resources