Skip to main content
Glama
maxnoller

Jules MCP Server

by maxnoller
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to Jules MCP Server

No user-submitted related servers found.

    Related Servers

    • Jules MCP Server

      MikBin
      A
      license
      A
      quality
      D
      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
      6 npm
      MIT

    • 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.
      2 npm
      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
      15 npm
      14
      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.
      32 npm
      4
      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

    A4/5.0

    Scored across 4 tools

    Disambiguation4/5

    The tools are mostly distinct: list_sessions and get_session clearly separate listing from detail retrieval. However, create_session and create_session_from_issue overlap in purpose, with the latter being a specialization, which could cause minor selection ambiguity.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern: create, list, get, create. Even the longer 'create_session_from_issue' maintains the convention with a clear prepositional modifier. There is no mixing of styles or vague verbs.

    Tool Count5/5

    With exactly 4 tools, the server is well-scoped for its purpose of managing Jules coding sessions. Each tool covers a distinct core operation without redundancy, making the count feel appropriate and not overwhelming.

    Completeness4/5

    The tool surface covers session creation (two variants), listing, and retrieval, which handles the primary lifecycle needs. However, it lacks explicit update or delete/cancel operations, which are minor gaps that could be worked around but are not covered.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources