Google Jules MCP

Automate Google Jules, the AI coding assistant, for tasks like code reviews, repository management, and AI-powered development workflows.

A Model Context Protocol (MCP) server for automating Google Jules - the AI coding assistant. This MCP enables seamless integration with Jules for task creation, code review automation, repository management, and AI-powered development workflows.

- Create Tasks: Automatically create Jules tasks with repository and description
- Monitor Progress: Track task status and get real-time updates
- Approve Plans: Review and approve Jules execution plans
- Resume Tasks: Resume paused or interrupted tasks
- Bulk Operations: Create multiple tasks efficiently

- Code Analysis: Analyze code changes and diffs
- Branch Management: Handle repository branches and configurations
- Source Navigation: Browse and analyze source files
- Review Automation: Automate code review workflows

- Send Messages: Send instructions and feedback to Jules
- Chat History: Track conversation history with Jules
- Context Extraction: Extract relevant context from task discussions

- Task Listing: List and filter tasks by status
- Progress Tracking: Monitor development progress across projects
- Data Persistence: Local storage of task data and history

- Node.js 18+
- TypeScript
- Git access to repositories you want to manage

# Clone the repository git clone https://github.com/samihalawa/google-jules-mcp.git cd google-jules-mcp # Install dependencies npm install # Build the project npm run build # Test the installation npm test

🔐 Session Management & Authentication

The MCP supports 5 different session management modes:

🌐Browserbase (Recommended for Smithery)

Perfect for remote deployments and cloud hosting:

SESSION_MODE=browserbase BROWSERBASE_API_KEY=bb_live_g3i-b4WPFh__E3cErKE5rO-jWds # Your API key BROWSERBASE_PROJECT_ID=d718e85f-be7b-497d-9123-b1bbf798f1bb # Your project ID BROWSERBASE_SESSION_ID= # Optional: use existing session

SESSION_MODE=chrome-profile CHROME_USER_DATA_DIR=/Users/yourname/Library/Application Support/Google/Chrome/Default

Save browser data to a specific directory:

SESSION_MODE=persistent CHROME_USER_DATA_DIR=~/.jules-mcp/browser-data # Custom browser data directory

Create a.envfile or set environment variables:

// Create a task to fix a bug { "name": "jules_create_task", "arguments": { "description": "Fix the login authentication bug in the user dashboard. The issue occurs when users try to log in with special characters in their password.", "repository": "mycompany/webapp", "branch": "main" } }

// Get task details and progress { "name": "jules_get_task", "arguments": { "taskId": "9103172019911831130" } }

// Send additional context or instructions { "name": "jules_send_message", "arguments": { "taskId": "9103172019911831130", "message": "Please also add unit tests for the authentication fix and ensure backward compatibility." } }

// Create multiple tasks at once { "name": "jules_bulk_create_tasks", "arguments": { "tasks": [ { "description": "Add dark mode support to the UI", "repository": "mycompany/frontend", "branch": "feature/dark-mode" }, { "description": "Optimize database queries for user search", "repository": "mycompany/backend", "branch": "performance/search" } ] } }

// List active tasks { "name": "jules_list_tasks", "arguments": { "status": "in_progress", "limit": 10 } }

{ "name": "jules_session_info", "arguments": {} }

The server provides useful resources for context:

- jules://schemas/task- Complete task data model
- jules://current/active-tasks- Live list of active tasks
- jules://templates/common-tasks- Template examples for common development tasks

The MCP includes templates for common development scenarios:

- Bug Fix:"Fix the [specific issue] in [filename]. The problem is [description]."
- Feature Add:"Add [feature name] functionality to [location]. Requirements: [list requirements]."
- Refactor:"Refactor [component/function] to improve [performance/readability/maintainability]."
- Testing:"Add comprehensive tests for [component/function] covering [test cases]."
- Documentation:"Update documentation for [component] to include [new features/changes]."

The MCP is fully configured for Smithery deployment with comprehensive session management:
- Fork/Clonethis repository
- Deploy to Smithery: Visitsmithery.aiand connect your repo
- Configure Session Managementin Smithery settings:

SESSION_MODE=browserbase BROWSERBASE_API_KEY=bb_live_g3i-b4WPFh__E3cErKE5rO-jWds BROWSERBASE_PROJECT_ID=d718e85f-be7b-497d-9123-b1bbf798f1bb

google-jules-mcp/ ├── src/ │ └── index.ts # Main MCP server implementation ├── docs/ │ └── referencerecordings/ # Browser automation references ├── scripts/ │ └── test-mcp.js # Testing script ├── dist/ # Compiled output ├── package.json ├── tsconfig.json └── smithery.yaml # MCP deployment config

# Run the test suite npm test # Build and test npm run build && npm test # Development mode with file watching npm run dev

- Built with theModel Context Protocol SDK
- Inspired by the tusclasesparticulares-mcp implementation patterns
- Browser automation powered byPlaywright

Token-efficient MCP server for GitHub source code exploration via tree-sitter AST parsing