Jules AI MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JULES_API_KEY | Yes | Your Jules API key. Obtain it from Settings > API Keys in the Jules console (jules.google). | |
| JULES_MOCK_MODE | No | When set to true, runs the server in local test/demo mode without consuming API credits. | false |
| JULES_API_BASE_URL | No | The base URL for the Jules API. | https://jules.googleapis.com/v1alpha |
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_create_taskB | Creates a new autonomous coding task for Google Jules AI. Jules will checkout the repo, inspect files, formulate an execution plan, and prepare a PR. |
| jules_list_tasksC | Lists recent and active coding tasks handled by Google Jules AI. |
| jules_get_task_statusB | Fetches real-time status, logs, current step progress, and proposed plan for a specific Jules task. |
| jules_approve_planA | Approves or rejects the execution plan formulated by Jules. Jules will not modify code until its plan is approved. |
| jules_send_feedbackB | Sends a steering message, guidance, or mid-session instruction to an ongoing Jules coding session. |
| jules_get_diffA | Fetches the git diff and PR link produced by Jules once execution or milestone steps have started. |
| jules_cancel_taskC | Aborts and cancels an active Jules autonomous coding task. |
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 7 tools
Each tool maps to a distinct action in the Jules task lifecycle: list, create, status, approve, feedback, diff, cancel. The read-style tools (get_task_status vs get_diff) are clearly distinguished by what they return, and approve_plan vs send_feedback are separated by their distinct purposes. No two tools can be reasonably confused.
All names follow a strict 'jules_verb_noun' snake_case pattern, e.g. jules_list_tasks, jules_create_task, jules_cancel_task. The prefix is applied uniformly and verbs are unambiguous. There is no deviation in style.
Seven tools is well-scoped for managing an autonomous coding-task lifecycle. Each tool earns its place with no redundancy or filler. This sits comfortably in the ideal range.
The set covers the full workflow: create, list, observe status, gate the plan via approval, steer mid-session, retrieve diffs/PR, and abort. Minor gaps remain, e.g. no explicit way to fetch or merge the final PR artifact once complete, but agents can work around this via get_diff.