Skip to main content
Glama
Sign In
Jules MCP Server

Jules MCP Server

by maxnoller
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Jules MCP Server

MCP (Model Context Protocol) server for Google Jules, the asynchronous AI coding agent. This server enables LLMs to create Jules sessions with automatic pull request creation.

Features

  • Auto-PR Creation: Sessions automatically create pull requests when complete

  • Issue Integration: Create sessions directly from GitHub issues

  • Session Management: List and monitor your Jules sessions

Related MCP server: Jules API MCP

Installation

npm install -g @anthropic/jules-mcp

Or run directly with npx:

npx @anthropic/jules-mcp

Configuration

Environment Variables

Variable

Required

Description

JULES_API_KEY

Yes

Jules API key from Google AI Studio

GITHUB_TOKEN

No

GitHub token for fetching issue details (optional but recommended)

Claude Code

Add to ~/.config/ccs/mcp.toml:

[servers.jules]
command = "npx @anthropic/jules-mcp"

[servers.jules.env]
JULES_API_KEY = "env://JULES_API_KEY"
GITHUB_TOKEN = "env://GITHUB_TOKEN"

Claude Desktop

Add to your Claude Desktop config:

{
  "mcpServers": {
    "jules": {
      "command": "npx",
      "args": ["@anthropic/jules-mcp"],
      "env": {
        "JULES_API_KEY": "your-api-key"
      }
    }
  }
}

Tools

create_session

Create a new Jules coding session.

Parameters:

  • repo (required): GitHub repository in owner/repo format

  • prompt (required): Task description for Jules

  • auto_pr (optional, default: true): Automatically create a PR when done

  • starting_branch (optional): Branch to start from

  • title (optional): Session title

Example:

{
  "repo": "myorg/myrepo",
  "prompt": "Add input validation to the login form",
  "auto_pr": true
}

create_session_from_issue

Create a session directly from a GitHub issue.

Parameters:

  • repo (required): GitHub repository in owner/repo format

  • issue_number (required): GitHub issue number

  • additional_context (optional): Extra instructions

Example:

{
  "repo": "myorg/myrepo",
  "issue_number": 42
}

list_sessions

List your Jules sessions.

Parameters:

  • limit (optional, default: 10): Maximum sessions to return

get_session

Get details of a specific session.

Parameters:

  • session_id (required): The session ID

Development

# Install dependencies
npm install

# Build
npm run build

# Run locally
JULES_API_KEY=your-key node dist/index.js

License

MIT

Available Tools

4 tools
create_sessionA

Create a new Jules coding session. Jules will clone the repo, execute the task, and optionally create a PR automatically.

Inputs: repo (required), prompt (required), title, auto_pr, +1 more.

create_session_from_issueA

Create a Jules session from a GitHub issue. Fetches issue details and creates a session with auto-PR.

Inputs: repo (required), issue_number (required), additional_context.

get_sessionA

Get details of a specific Jules session including status and PR info

Inputs: session_id (required).

list_sessionsA

List your Jules sessions with their status

Inputs: limit.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Deploy Server
    Claude Code, inside the Godot 4 editorFlockbay puts an AI agent in the real Godot 4 editor: it writes GDScript, runs your game and fixes what breaks. Free, or bring your own Claude Code or Codex.flockbay.comAd

    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 recent community issues

    Resources

    Related MCP Connectors

    Related MCP Servers

    • 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
      13 npm
      14
      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.
      10 npm
      MIT

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