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 repository names (e.g., owner/repo1,owner/repo2). If set, only these repos can be modified | |
| JULES_DEFAULT_BRANCH | No | Optional default branch for repository operations | 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
Server capabilities have not been inspected yet.
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
Most tools have distinct purposes, but 'create_coding_task' and 'schedule_recurring_task' could be confused as both initiate tasks, though one is immediate and the other scheduled. The other tools (delete_schedule, get_session_status, list_schedules, manage_session) are clearly differentiated by their specific actions on sessions or schedules.
All tools follow a consistent verb_noun pattern with snake_case (e.g., create_coding_task, delete_schedule, get_session_status). The naming is predictable and readable across all six tools, making it easy for agents to understand their functions.
With 6 tools, the server is well-scoped for managing Jules coding sessions and scheduled tasks. Each tool serves a clear purpose (e.g., creation, deletion, listing, status checking, management), and there are no redundant or trivial tools, making the count appropriate for the domain.
The toolset covers core operations for sessions (create, get status, manage) and schedules (list, delete, schedule recurring), but there is a minor gap: no tool explicitly updates or modifies existing scheduled tasks beyond deletion. However, agents can work around this by deleting and re-creating schedules, so coverage is largely complete for the apparent domain.