Google Jules MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JULES_API_KEY | Yes | A valid Google Jules API key |
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 | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| jules_list_accountsA | List all configured Google Jules / GitHub accounts and routing aliases in the system. |
| jules_list_sourcesA | List all GitHub repositories connected to Google Jules for a specific account or across defaults. |
| jules_delegate_taskA | Delegate an autonomous coding, refactoring, bug-fixing, or documentation task to Google Jules. Jules will spin up a Google Cloud VM sandbox, clone the repo, plan changes, run test commands, apply modifications, and open a Pull Request automatically. Includes prompt boosting & verification contracts. |
| jules_get_sessionA | Retrieve status, generated outputs, Pull Request links, and metadata for a specific Jules session. |
| jules_list_sessionsA | List recent active and completed Jules sessions for an account. |
| jules_list_activitiesA | Get the chronological event timeline of a session (agent thoughts, execution plans, bash outputs, diffs, PRs). |
| jules_approve_planA | Approve the generated execution plan for a session paused in AWAITING_PLAN_APPROVAL state. |
| jules_send_messageB | Send follow-up guidance, feedback, or adjustments to an ongoing Jules session. |
| jules_get_diffA | Extract the unified git patch diff from a completed or active Jules session. |
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 9 tools
Each tool targets a distinct resource or action: accounts, sources, task delegation, session retrieval, session listing, activity timelines, plan approval, messaging, and diff extraction. There is minimal overlap, and any possible confusion between get_session, list_sessions, and list_activities is resolved by their distinct purposes.
All tools follow the consistent 'jules_verb_noun' pattern with snake_case, making the naming predictable and easy to navigate. For example, list_accounts, delegate_task, get_session, and approve_plan all use the same verb-first convention.
With 9 tools, the set is well-scoped for managing Google Jules sessions, covering account/source introspection, task delegation, monitoring, and interaction. The count is within the ideal 3-15 range and each tool earns its place.
The lifecycle covers delegation, monitoring (status, activities, diffs), approval, and follow-up messaging. A minor gap is the absence of a cancel/stop session operation, but the existing surface handles the primary workflows effectively.