Google Jules MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GOOGLE_JULES_API_KEY | Yes | Your 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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| jules_list_sourcesA | List all available sources (GitHub repositories) connected to Jules. Returns a list of sources with their names and GitHub repo details. |
| jules_get_sourceA | Get details of a specific source by its name. Returns source information including GitHub repo owner, name, branches, and privacy status. |
| jules_list_sessionsA | List all sessions. Sessions are continuous units of work within a specific context. Returns session details including state, outputs, and pull requests. |
| jules_get_sessionA | Get details of a specific session including its state, source context, outputs, and any pull requests created. |
| jules_create_sessionA | Create a new Jules session to start a coding task. Jules will work on the task autonomously, optionally creating a PR when done. |
| jules_approve_planB | Approve a plan in a session that requires plan approval. This allows Jules to proceed with executing the plan. |
| jules_send_messageA | Send a message to Jules within an active session. Use this to provide feedback, ask questions, or request changes. |
| jules_list_activitiesC | List all activities within a session. Activities include plan generation, progress updates, messages, and completion status. |
| jules_get_activityA | Get details of a specific activity within a session, including artifacts like code changes, bash outputs, or media. |
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 has a distinct purpose: session operations, activity tracking, source management, and messaging. There is no overlap, and descriptions clearly differentiate them.
All tools follow a consistent 'jules_verb_noun' pattern in snake_case, making it easy to predict and understand the tool's function from its name.
With 9 tools, the server is well-scoped for its domain. The number is within the ideal range and each tool serves a clear role without redundancy.
The tool set covers session lifecycle, activity details, and source management. Minor gaps like delete operations exist but do not hinder core workflows.