Jules MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JULES_CONFIG | No | Path to config.json. | config.json |
| JULES_API_KEY | Yes | API key for Jules API authentication. | |
| JULES_API_BASE | No | Base URL for 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 | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| jules_create_sessionC | Create a new Jules coding session for a GitHub repository |
| jules_get_sessionB | Fetch session metadata, state, and outputs |
| jules_check_julesA | Token-saving status check. Returns a one-letter code: Q (needs clarification), C (completed), F (failed), N (nothing to do). Provide session_id directly or owner/repo to auto-resolve the current project session. |
| jules_list_sessionsA | List Jules sessions. By default only non-archived sessions are returned (Jules API default). Set includeArchived=true to also return archived sessions, or pass a raw AIP-160 filter (e.g. 'archived = true'). |
| jules_delete_sessionB | Delete a Jules session |
| jules_send_messageB | Send a clarification or instruction to a Jules session |
| jules_approve_planA | Approve the plan for a session awaiting plan approval |
| jules_list_activitiesC | List activities for a Jules session |
| jules_get_activityA | Get a single activity by ID for a Jules session |
| jules_list_sourcesB | List available sources (GitHub repositories) |
| jules_get_sourceB | Get details for a specific source |
| jules_extract_pr_from_sessionA | Extract pull request and/or change set information from a completed Jules session's outputs. Returns the full pull request (url, title, description, baseRef, headRef) when AUTO_CREATE_PR was used, and the change set (git patch, suggested commit message) when present. Sessions that produced a patch but no PR still return their changeSet. |
| jules_waitA | Pause execution for a given number of seconds (max 600). Use between polling calls to conserve context window tokens instead of requiring a separate sleep MCP server. |
| jules_monitor_sessionA | Polls a Jules session until it reaches a terminal state (COMPLETED or FAILED), sending MCP progress notifications with the latest activity. Returns the final session state and outputs. |
| jules_archive_sessionA | Archive a Jules session. Archived sessions are hidden from the default session list (the Jules API list defaults to non-archived only). Use jules_unarchive_session to restore. |
| jules_unarchive_sessionA | Restore an archived Jules session so it reappears in the default session list. |
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 16 tools
Most tools map to a distinct resource and action: session CRUD, activities, sources, PR extraction, and monitoring are clearly separated. The only mild ambiguity is among get_session, check_jules, and monitor_session, since all report session status, but their one-shot vs. lightweight vs. polling semantics are clear from the descriptions.
The set consistently uses a jules_ prefix and snake_case verb_noun style, making the general pattern predictable. jules_check_jules and jules_wait deviate slightly from the verb_noun convention, and the duplicated 'Jules' in check_jules is awkward, but these are minor exceptions.
16 tools is slightly above the ideal 3-15 range, but the count is justified by the server's scope: session lifecycle, activity inspection, source lookup, PR extraction, and a polling/monitoring utility all require distinct tools. There is no obvious filler or redundant bloat.
The tool set covers the full Jules session workflow: create, read, list, delete, archive, unarchive, communicate, approve plans, monitor, inspect activities, extract PRs, and resolve sources. The included wait and monitor utilities prevent dead ends when handling asynchronous sessions.