Jules MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CACHE_TTL | No | Cache time-to-live (seconds) | 3600 |
| LOG_LEVEL | No | Logging level | INFO |
| SERVICE_PORT | No | Server port | 8085 |
| JULES_API_KEY | Yes | Your Jules API key. Get it from: https://jules.google.com/settings#api | |
| DAILY_COST_LIMIT | No | Daily cost limit | 100.00 |
| MAX_COST_PER_HOUR | No | Cost limit per hour | 10.00 |
| JULES_API_BASE_URL | No | API endpoint | https://jules.googleapis.com |
| RATE_LIMIT_REQUESTS | No | Requests per minute | 60 |
| COST_TRACKING_ENABLED | No | Enable cost tracking | true |
| CODE_VALIDATION_ENABLED | No | Enable code validation | true |
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_create_workerC | Create a new Jules worker session for a task |
| jules_send_messageC | Send a message to an existing Jules worker session |
| jules_get_activitiesC | Get recent activities for a Jules worker |
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 3 tools
Each tool has a clearly distinct purpose: creating a worker, getting activities, and sending messages. There is no overlap in functionality, and the descriptions make it easy to tell them apart.
All tools follow a consistent 'jules_verb_noun' pattern with snake_case, using clear verbs like create, get, and send. The naming is predictable and uniform throughout the set.
With only 3 tools, the set feels thin for a worker session management domain. While it covers basic operations, it lacks tools for updating, deleting, or managing worker states, which might limit agent workflows.
The tool surface is significantly incomplete for managing Jules workers. It includes create, get activities, and send message, but misses essential operations like updating worker settings, deleting sessions, listing workers, or handling errors, which could cause agent failures.