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 |
Capabilities
Features and capabilities supported by this server
| 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 | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/analisaperlengkapan/mcp-jules'
If you have feedback or need assistance with the MCP directory API, please join our Discord server