Google Jules MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| DEBUG | No | Enable debug mode with screenshots (true/false). | false |
| TIMEOUT | No | Browser timeout in milliseconds (default: 30000). | 30000 |
| HEADLESS | No | Run browser in headless mode (true/false). | true |
| COOKIES_PATH | No | File path to save/load cookies (default: ~/.jules-mcp/cookies.json). | ~/.jules-mcp/cookies.json |
| SESSION_MODE | No | Session management mode to use. Options: fresh, chrome-profile, cookies, persistent, browserbase. | |
| JULES_DATA_PATH | No | Custom data storage path for task data and history. | ~/.jules-mcp/data.json |
| BROWSERBASE_API_KEY | No | API key for Browserbase, required if SESSION_MODE is 'browserbase'. | |
| GOOGLE_AUTH_COOKIES | No | Google authentication cookies string, required if SESSION_MODE is 'cookies'. | |
| CHROME_USER_DATA_DIR | No | Path to Chrome user data directory, required if SESSION_MODE is 'chrome-profile' or 'persistent'. | |
| BROWSERBASE_PROJECT_ID | No | Project ID for Browserbase, required if SESSION_MODE is 'browserbase'. | |
| BROWSERBASE_SESSION_ID | No | Optional existing Browserbase session ID to reuse. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| jules_create_taskC | Create a new task in Google Jules with repository and description |
| jules_get_taskC | Get details of a specific Jules task by ID or URL |
| jules_list_tasksB | List all Jules tasks with their status |
| jules_send_messageB | Send a message/instruction to Jules in an active task |
| jules_approve_planC | Approve Jules execution plan for a task |
| jules_resume_taskB | Resume a paused Jules task |
| jules_analyze_codeC | Analyze code changes and diff in a Jules task |
| jules_bulk_create_tasksB | Create multiple tasks from a list of descriptions and repositories |
| jules_session_infoA | Get current session configuration and authentication status |
| jules_setup_wizardC | Interactive session setup wizard for automated Google authentication configuration |
| jules_get_cookiesB | Extract current browser cookies for session persistence and backup |
| jules_set_cookiesB | Set browser cookies from string or JSON for authentication |
| jules_screenshotC | Take a screenshot of current Jules page for debugging and verification |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Task Schema | Complete task model with all available attributes |
| Active Tasks | Live list of active tasks in Jules |
| Common Task Templates | Template examples for common development tasks |
| Session Setup Automation | Step-by-step prompts for automated Google authentication setup |
| Cookie Extraction Guide | Automated prompts for extracting Google authentication cookies |
| Browserbase Configuration | Automated Browserbase setup for remote browser sessions |
| Session Mode Selection Guide | Intelligent guide for choosing the optimal session management mode |
| Authentication Troubleshooting | Automated diagnostics and fixes for authentication issues |
TDQS
Scored across 13 tools
Most tools are clearly distinct (create/get/list/send/approve/resume/analyze), but jules_get_cookies and jules_set_cookies could be confused with session management or authentication setup, and jules_screenshot is a debugging aid that overlaps somewhat with jules_analyze_code in purpose. Overall, the core task lifecycle tools are unambiguous.
The naming follows a consistent jules_verb_noun pattern (create_task, get_task, list_tasks, send_message, approve_plan, resume_task, analyze_code). Minor deviations: jules_bulk_create_tasks is a variant of create, and jules_setup_wizard, jules_get_cookies, jules_set_cookies, jules_screenshot are less verb-noun consistent but still readable.
13 tools is within the well-scoped range, and each tool serves a distinct function in the Jules workflow. The count is slightly on the higher side due to session/cookie/screenshot utilities, but they are justifiable for a browser-automation-based MCP server.
The core task lifecycle is covered: create, get, list, send message, approve plan, resume, analyze. Missing operations like cancel/delete task or update task description are minor gaps. The authentication/session tools (setup_wizard, cookies) add completeness for the browser-based setup domain.