Jules MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JULES_API_KEY | Yes | Your Google Jules API key used for authentication with the Jules AI service. |
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_sessionsC | List sessions with optional automatic pagination to retrieve sessions natively. |
| get_sessionB | Get details for a single session by ID or resource name. |
| create_sessionC | Create a new Jules session for a given source and prompt. |
| delete_sessionB | Delete a completed or terminated session by ID. |
| clean_completed_sessionsB | Scans all sessions and deletes completed, terminated, failed, or inactive sessions automatically. |
| list_activitiesC | List activities for a specific session. |
| get_activityC | Get details for a single activity by ID. |
| list_all_activitiesC | List all activities for a session with automatic pagination. |
| approve_session_planC | Approve the generated plan for a session in a single native MCP call. |
| send_session_messageC | Send a user message (prompt) to an existing session. |
| list_sourcesC | List sources with optional filter and pagination. |
| get_sourceC | Get details for a single source by ID. |
| get_all_sourcesC | Get all sources with optional filtering (auto-pagination). |
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 13 tools
Several tools have unclear boundaries, especially list_activities vs list_all_activities and list_sources vs get_all_sources, which appear to perform nearly the same listing operation with only subtle pagination differences. Descriptions do not clearly explain when to choose one over the other.
Most names follow a consistent snake_case verb_noun pattern (list_sessions, get_session, create_session, delete_session). Minor deviations exist: get_all_sources uses 'get' for a list operation, and list_all_activities/list_activities plus list_sources/get_all_sources introduce inconsistent list vs get_all phrasing.
13 tools is reasonable for a session/activity/source management server. However, the redundant auto-pagination variants slightly inflate the count, meaning not every tool clearly earns its place.
Core session lifecycle is covered with create, get, list, delete, bulk cleanup, plan approval, and messaging. Activities and sources are read/list-oriented, which may be appropriate if they are externally managed, but there is no update or termination operation beyond delete.