Skip to main content
Glama
Godzilla675

Google Jules MCP Server

by Godzilla675

Related Servers

Alternatives to Google Jules MCP Server

No user-submitted related servers found.

    Related Servers

    • F
      license
      A
      quality
      D
      maintenance
      Enables LLM applications to interact with Google's Jules AI coding assistant to manage repositories, coding sessions, and pull requests. It allows users to programmatically create tasks, approve plans, and communicate with the assistant during active coding sessions.
      9
      -
    • A
      license
      B
      quality
      C
      maintenance
      Exposes Google Jules AI capabilities for automated coding tasks, including session management, code reviews, and unified diff handling. It enables users to create sessions, approve plans, and synchronize AI-generated code changes with GitHub repositories.
      26
      3 npm
      MIT
    • -
      license
      A
      quality
      Not graded
      maintenance
      Enables automation of Google Jules AI coding assistant through task creation, code review automation, repository management, and AI-powered development workflows. Supports multiple session modes including cloud deployment with persistent authentication.
      13
      -
    • A
      license
      Not graded
      quality
      F
      maintenance
      Connects AI coding assistants to the Jules API for autonomous coding sessions. Enables creating and managing coding sessions, GitHub integration, plan approval workflows, and real-time activity tracking directly from your IDE.
      3 npm
      6
      MIT
    • F
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to interact with Google's Jules coding agent API for autonomous coding tasks, allowing users to delegate bug fixes, refactoring, testing, and feature development with scheduling capabilities and human-in-the-loop approval workflows.
      6
      1
      -

    TDQS

    A3.8/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool has a distinct purpose: session operations, activity tracking, source management, and messaging. There is no overlap, and descriptions clearly differentiate them.

    Naming Consistency5/5

    All tools follow a consistent 'jules_verb_noun' pattern in snake_case, making it easy to predict and understand the tool's function from its name.

    Tool Count5/5

    With 9 tools, the server is well-scoped for its domain. The number is within the ideal range and each tool serves a clear role without redundancy.

    Completeness4/5

    The tool set covers session lifecycle, activity details, and source management. Minor gaps like delete operations exist but do not hinder core workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues