Jules MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | Port number for HTTP transport (used with --http flag) | 8080 |
| JULES_API_KEY | Yes | Your Jules API key from https://jules.google.com/settings |
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_sessionA | Create a new coding session with Jules AI coding agent. A session represents a unit of work where Jules executes a coding task on your repository. Args:
Returns: The created session with ID, state, and URL. Examples:
|
| jules_list_sessionsA | List all coding sessions for the authenticated user. Args:
Returns: List of sessions with ID, title, state, and timestamps. Includes nextPageToken if more results exist. Examples:
|
| jules_get_sessionA | Get details of a specific coding session. Args:
Returns: Full session details including:
Examples:
|
| jules_delete_sessionA | Delete a coding session. Args:
Returns: Confirmation of deletion. Note: This action cannot be undone. |
| jules_send_messageA | Send a message to an active Jules session. Use this to provide feedback, answer questions, or give additional instructions while Jules is working on a task. Args:
Returns: Confirmation that the message was sent. Examples:
|
| jules_approve_planA | Approve a pending plan in a Jules session. Only needed when the session was created with requirePlanApproval=true. After approval, Jules will execute the planned steps. Args:
Returns: Confirmation that the plan was approved. Note: Check session state is 'AWAITING_PLAN_APPROVAL' before calling. |
| jules_list_activitiesA | List all activities for a Jules coding session. Activities track everything that happens during a session:
Args:
Returns: List of activities with type, description, and timestamps. Examples:
|
| jules_get_activityA | Get details of a specific activity in a Jules session. Retrieves full details including artifacts like code changes, bash output, or media files. Args:
Returns: Full activity details including:
Examples:
|
| jules_list_sourcesA | List all repository sources connected to Jules. Sources are GitHub repositories that Jules can work with. Sources are connected through the Jules web interface. Args:
Returns: List of sources with repository details:
Examples:
|
| jules_get_sourceA | Get details of a specific repository source. Retrieves full information about a connected GitHub repository including all available branches. Args:
Returns: Full source details:
Examples:
|
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 10 tools
Each tool targets a distinct resource-action pair: sessions (create/get/list/delete/send/approve), activities (list/get), and sources (list/get). No two tools overlap in purpose, and descriptions clearly indicate which resource each operates on.
All tool names follow the consistent jules_<verb>_<noun> pattern in snake_case, with verbs like get, list, create, delete, send, and approve. This makes the API highly predictable and easy to navigate.
With 10 tools, the server is well-scoped for its purpose of managing AI coding sessions. Each tool has a clear, non-redundant role, covering session lifecycle, activity monitoring, and source context without unnecessary bloat.
The session lifecycle is well covered: create, read, list, delete, message, and plan approval. Activity and source listing/retrieval support monitoring and context. The only notable gap is a dedicated cancel/stop session tool, though sending a message could serve that purpose.