Jules MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| JULES_API_KEY | Yes | Your Jules API key (required). Generate at https://jules.google/settings | |
| JULES_ALLOWED_REPOS | No | Optional security allowlist (comma-separated repo names). If set, only these repos can be modified. Example: owner/repo1,owner/repo2 | |
| JULES_DEFAULT_BRANCH | No | Optional default branch name | main |
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 | {} |
| logging | {} |
| prompts | {} |
| resources | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| create_coding_taskA | Creates a new Jules coding session. Returns immediately with a session ID. Monitor progress via jules://sessions/{id}/full resource. |
| manage_sessionC | Manage an active Jules session: approve plans or send feedback |
| get_session_statusC | Get the current status and state of a Jules session |
| schedule_recurring_taskC | Schedule a Jules task to run automatically on a cron schedule. The server manages execution even when offline. |
| list_schedulesB | List all locally-managed scheduled tasks |
| delete_scheduleC | Delete a scheduled task by name |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| refactor_module | Guide for refactoring a specific module in a repository with clear goals |
| setup_weekly_maintenance | Set up automated weekly maintenance tasks for a repository |
| audit_security | Create a comprehensive security audit task with best practices |
| fix_failing_tests | Task template for fixing test failures |
| update_dependencies | Update dependencies with breaking change handling |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| Connected Repositories | List of GitHub repositories connected to Jules |
| Recent Sessions | Summary of recent Jules coding sessions |
| Scheduled Tasks | Locally-managed recurring Jules tasks |
| Schedule Execution History | History of scheduled task executions |
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose with no overlap: create_coding_task initiates sessions, get_session_status monitors them, manage_session controls them, while list_schedules, schedule_recurring_task, and delete_schedule handle scheduling separately. The descriptions reinforce these boundaries, making misselection unlikely.
The tools follow a consistent verb_noun pattern with snake_case throughout, such as create_coding_task and list_schedules. However, manage_session deviates slightly by using a more generic verb compared to the others, but overall the naming is predictable and readable.
With 6 tools, the server is well-scoped for managing Jules coding sessions and scheduled tasks. Each tool earns its place by covering distinct aspects like creation, monitoring, management, and scheduling, without being overly sparse or bloated.
The tool set provides solid coverage for session lifecycle (create, status, manage) and scheduling (list, create, delete), with no dead ends. A minor gap exists in lacking a direct tool to list or delete sessions, but agents can infer status from get_session_status and deletion might be handled implicitly.