jules-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| jules_check_eventsA | Real-time event monitor across all Google accounts in the pool: detects sessions that are stuck (asking questions), awaiting plan approval, completed (with PR/patch details), or failed. The primary harness tool for 'Is Jules done? Is Jules stuck?'. |
| jules_auto_nudge_allA | Autonomous unblocker: automatically finds all sessions currently stuck in AWAITING_USER_FEEDBACK across the entire pool and sends a pre-emptive unblocking directive to keep Jules working without manual CLI nudging. |
| jules_wait_for_taskB | Synchronously poll/wait for a Google Jules session until completion, failure, plan approval request, or question asking. Bridges async cloud execution directly into harness dialogue. |
| jules_dispatch_and_waitA | Create a new Jules coding task and immediately block/wait for it in a single MCP tool call. Automatically injects architectural invariants, sandbox test runner commands, and anti-pause directives. |
| jules_recipe_dispatchC | Dispatch a standardized, high-efficiency chore recipe with pre-tested prompt blueprints (e.g. 'scaffold-unit-test', 'add-strict-types', 'document-endpoints', 'clean-dead-code', 'refactor-isolated-helper'). Eliminates prompt ambiguity and ensures optimal output quality. |
| jules_verify_patchA | Dry-run preflight check: inspects a completed session's git patch and runs 'git apply --check --3way' against a local workspace to verify whether the patch will apply cleanly with 0 conflicts before creating branches or writing files. |
| jules_consolidate_sessionsA | Reconcile and merge multiple concurrent Jules sessions on the SAME repository into a single clean local branch or unified PR. Uses 3-way unidiff application to resolve cloud branch drift automatically, runs tests, and creates 1 clean PR without merge conflicts. |
| jules_rebase_prA | Rebase an existing Jules GitHub PR against the latest base branch (e.g. main) locally and force-push with lease, eliminating PR collision and out-of-date branch warnings on GitHub. |
| jules_queue_tasksA | Execute a sequence of chores sequentially on a repository: waits for Task N to complete before launching Task N+1, preventing branch drift and merge conflicts across PRs. |
| jules_stream_progressA | Extract a structured markdown progress breakdown for a session: step-by-step plan completion checklist [x], thought reasoning trail, files modified, and sandbox commands executed. |
| jules_apply_patchA | Fetch the clean git unidiff patch from a completed Jules session and apply it directly to a local repository workspace, with optional branch creation, test execution, and auto-commit using 3-way merge. |
| jules_review_prA | Inspect and review a GitHub PR opened by Google Jules: pulls PR metadata, review comments, diff stats, and CI status checks via 'gh'. |
| jules_merge_prA | Safely squash-merge a verified GitHub PR opened by Google Jules and delete the remote branch via 'gh'. |
| jules_list_sourcesA | List all connected GitHub repositories and sources across all configured Google Jules accounts, including branch metadata, pagination, and AIP-160 filter support. |
| jules_get_sourceA | Get detailed metadata, all available branches, default branch, and privacy status for a specific connected repository. |
| jules_create_taskA | Dispatch an asynchronous coding chore to Google Jules. Automatically decorates prompt with system invariants, sandbox test runners, and anti-pause directives. |
| jules_batch_dispatchB | Dispatch multiple coding tasks across repositories simultaneously, load-balancing automatically across all Google accounts in the pool. |
| jules_list_sessionsA | List and filter all coding sessions across all pooled Google accounts by state, repository source, AIP-160 filter, or pagination token. |
| jules_get_sessionA | Retrieve comprehensive details for a specific session ID: status, PR URL, git patch diff, Jules Web URL, failure reason, and activity timeline. |
| jules_list_activitiesA | List and stream the full chronological activity trail for a session (agent thoughts, progress updates, bash outputs, user messages, plan events) with pagination and AIP-160 filters. |
| jules_get_activityA | Retrieve a single specific activity event payload by its session ID and activity ID. |
| jules_get_planA | Extract the structured, numbered step-by-step execution plan generated by Jules for a session. |
| jules_approve_planA | Approve a multi-step execution plan generated by Jules so it can begin implementing changes. |
| jules_reply_feedbackA | Send user feedback, unblocking clarification, or follow-up steering instructions directly to an in-progress or paused session. |
| jules_get_patchA | Extract the clean git unidiff patch and suggested commit message directly from a completed session. |
| jules_inspect_bash_logsA | Extract all terminal shell commands executed inside Google's cloud sandbox, along with exit codes and stdout/stderr output. |
| jules_get_media_artifactsA | Extract visual media artifacts (screenshots, UI renderings, test failure images) generated by Jules in the sandbox. |
| jules_archive_sessionB | Archive or unarchive a session in Google Jules. |
| jules_delete_sessionA | Permanently delete a session from Google Jules across accounts. |
| jules_sync_prsB | Run local autopilot: extract patches, verify locally with tests, and open GitHub PRs via 'gh'. |
| jules_pool_statusA | Check the health, rolling 24-hour quota ledger, active vs completed count, and remaining capacity across all Google accounts in the pool. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 31 tools
Most tools map to distinct resources or lifecycle stages, and the dispatch family is differentiated by concurrency and wait semantics. A few pairs, such as check_events vs wait_for_task and verify_patch vs apply_patch, could cause confusion, but the descriptions are generally clear enough to guide selection.
All tools share the jules_ snake_case prefix and mostly follow a verb_object pattern, with predictable list/get and create/dispatch groupings. Exceptions like recipe_dispatch, batch_dispatch, pool_status, and auto_nudge_all break the strict verb-first convention but remain readable.
At 31 tools, the surface feels heavy and exceeds the typical well-scoped range. Several highly granular tools such as get_activity, get_media_artifacts, and inspect_bash_logs could plausibly be consolidated without losing core functionality, though the broad Jules lifecycle domain does justify some of the count.
The tool set covers the full session lifecycle from dispatch through waiting, monitoring, patching, PR management, archival, and deletion. Notable gaps include no explicit cancel/abort running session and no source creation or connection management, but these are mostly peripheral to the core automation workflow.