Skip to main content
Glama

Deprecated Use Instead

⚠️ Deprecated Notice

Jules MCP is now deprecated. Google Labs has released their official Jules SDK with native Model Context Protocol (MCP) support, making this community package obsolete.

NPM Version License: MIT TypeScript Model Context Protocol

🗺️ Navigation


⚙️ Setup

Choose the installation method that fits your workflow. Both methods require a Jules API Key.

IMPORTANT

Visitjules.google.com/settings/api to generate your credentials before proceeding.

The fastest way to get started. Copy the block below and paste it into your AI assistant (Antigravity, Cursor, or Claude).

Read https://raw.githubusercontent.com/TheRealAshik/jules-mcp/refs/heads/main/docs/AGENT_INSTALL.md and do as per the instructions.

If you prefer to configure the server yourself, follow these steps:

  1. Locate your config file:

    • Antigravity: ~/.gemini/antigravity/mcp_config.json

    • Claude Desktop: %APPDATA%\Claude\claude_desktop_config.json

    • Cursor: Settings > Features > MCP > Add New Server

  2. Add the following snippet:

{
  "mcpServers": {
    "jules-mcp": {
      "command": "npx",
      "args": ["-y", "@realashik/jules-mcp"],
      "env": {
        "JULES_API_KEY": "YOUR_API_KEY_HERE"
      }
    }
  }
}

📖 Overview

Jules MCP is a Model Context Protocol (MCP) server designed to supercharge AI coding agents to control Jules. While standard AI agents are limited to linear task execution, Jules MCP introduces Staged Orchestration—enabling a "Commander" agent to deploy multiple specialized sub-agents (Maestros, Crews, Freelancers) to handle distinct parts of a project simultaneously or in sequence.

Built on top of the official @google/jules-sdk, it provides the bridge between your IDE and a distributed team of AI workers with advanced features like real-time streaming, session management, and intelligent caching.

TIP

Use IDE agents to analyse and assign tasks to Jules to get best output from this MCP.

NOTE

v1.0.4+ now uses the official Google Jules SDK for improved reliability, streaming support, and better error handling.


🚀 Features

  • 🎭 Multi-Role Orchestration: Spawn MAESTRO (Architect), CREW (Implementer), FREELANCER (Specialist), or EVALUATOR (Quality Control).

  • 📝 Staged Workflows: Automatically manage git branches, code generation, and merging in a single, safe flow.

  • 🧠 Global Shared Memory: Cross-session memory allows workers to pass variables and context like biological collaborators.

  • 🛡️ Quality Enforcement: Built-in review cycles ensure code meets security and performance standards before merging.

  • ⚡ Zero Configuration: Instantly usable via npx with automatic environment discovery.

  • 🌊 Real-time Streaming: Stream live activity updates from Jules sessions using the official SDK.

  • 🔄 Session Management: Simplified session lifecycle with automatic polling and state management.


🌟 Support

If Jules MCP helps you build faster, please consider:

Developed with ❤️ by TheRealAshik

Available Tools

3 tools
jules_create_workerC

Create a new Jules worker session for a task

Inputs: task_description (required), source (required), title (required), github_branch, +2 more.

jules_get_activitiesC

Get recent activities for a Jules worker

Inputs: session_id (required), limit.

jules_send_messageC

Send a message to an existing Jules worker session

Inputs: session_id (required), message (required).

Tool Schema Changelog

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

Loading tool schema changelog…

    TDQS

    B3.2/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: creating a worker, getting activities, and sending messages. There is no overlap in functionality, and the descriptions make it easy to tell them apart.

    Naming Consistency5/5

    All tools follow a consistent 'jules_verb_noun' pattern with snake_case, using clear verbs like create, get, and send. The naming is predictable and uniform throughout the set.

    Tool Count3/5

    With only 3 tools, the set feels thin for a worker session management domain. While it covers basic operations, it lacks tools for updating, deleting, or managing worker states, which might limit agent workflows.

    Completeness2/5

    The tool surface is significantly incomplete for managing Jules workers. It includes create, get activities, and send message, but misses essential operations like updating worker settings, deleting sessions, listing workers, or handling errors, which could cause agent failures.

    Related MCP Connectors