Skip to main content
Glama
Toligrim

Jules MCP

by Toligrim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to Jules MCP

No user-submitted related servers found.

    Related Servers

    • jules-mcp

      jbolt25
      F
      license
      B
      quality
      B
      maintenance
      Enables Codex to interact with Google Jules through MCP, allowing discovery of connected GitHub repositories, starting coding sessions, monitoring activity, sending follow-up instructions, approving plans, and retrieving results and pull-request links.
      8
      -

    • 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.
      5 npm
      MIT

    • Jules MCP Server

      streetquant
      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
    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.5/5.0

    Scored across 11 tools

    Disambiguation4/5

    Most tools map clearly to distinct resource/action pairs (list/get sources, sessions, activities), and the workflow actions (create, send_message, approve_plan, wait) are unambiguous. The only mild overlap is jules_session_snapshot, which combines get_session and list_activities, and jules_wait_for_session, which could be approximated by polling activities.

    Naming Consistency4/5

    Names consistently use a jules_ prefix with snake_case, mostly following an action_noun pattern (list_sources, get_session, create_session, approve_plan). jules_session_snapshot breaks the verb-first convention, and jules_wait_for_session inserts a preposition, but the overall style remains predictable.

    Tool Count5/5

    Eleven tools is well within the ideal range and matches the server's scope of managing sources, sessions, activities, and approval/waiting workflows. Each tool addresses a distinct need without unnecessary bloat.

    Completeness4/5

    The surface covers listing/retrieving sources and sessions, creating sessions, sending feedback, approving plans, and inspecting activities, which is strong coverage for a coding-agent API. A minor gap is the lack of an explicit cancel/terminate session tool, though agents could work around it via send_message or waiting.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources