Jules

You can run a local, autonomous MCP server that connects to Jules through a lightweight, persistent scheduling engine. This server lets you create, schedule, monitor, and approve coding tasks with Jules from your AI assistant while keeping control over when and how changes are made.

How to use

Use the Jules MCP Server with your MCP client to create coding tasks, schedule recurring maintenance, monitor progress, and approve plans. You will issue natural language prompts to your AI assistant, which will translate them into Jules actions, display status updates, and let you review plans before changes go live.

How to install

Prerequisites you need before installing are as follows.

# Prerequisites
- Node.js 18.0.0 or higher
- Jules API Key obtained from Jules settings
- GitHub repositories linked to Jules via the web UI

# Setup
# 1. Clone or download this project
cd jules-mcp

# 2. Install dependencies
npm install

# 3. Build TypeScript
npm run build

# 4. Set your API key
export JULES_API_KEY="your-key-here"

# 5. Test the server
npm start

Configuration and startup notes

Configure environment variables and client integrations to secure and optimize interactions with Jules. The key values you set here control which repositories can be modified and how the server authenticates with Jules.

# Environment setup examples
# Required
JULES_API_KEY=your_jules_api_key_here

# Optional - restrict which repos can be modified
JULES_ALLOWED_REPOS=owner/repo1,owner/repo2

# Optional - default branch to target when creating tasks
JULES_DEFAULT_BRANCH=main

Claude Desktop configuration

To run the Jules MCP Server from Claude Desktop, add a server entry that points to the local build of the MCP server.

{
  "mcpServers": {
    "jules": {
      "command": "node",
      "args": ["/path/to/jules-mcp/dist/index.js"],
      "env": {
        "JULES_API_KEY": "your-key-here"
      }
    }
  }
}

On macOS: ~/Library/Application Support/Claude/claude_desktop_config.json On Windows: `%APPDATA%/Claude/claude_desktop_config.json

## VS Code / Cursor configuration

If you use Cursor or VS Code with MCP support, configure the MCP server with the appropriate command and environment.

{ "mcp.servers": { "jules": { "command": "jules-mcp", "env": { "JULES_API_KEY": "your-key-here" } } } }

## Usage tips

You can create immediate tasks, schedule recurring tasks, monitor progress, and review/approve Jules plans. The system maintains a local schedule store that survives restarts and can be observed via the available resources and sessions endpoints.

## Available Resources

Read-only context available to the AI includes connected repositories, recent sessions, full session details, active schedules, and execution history.

## Available Tools

This section is described in the tooling metadata and is not printed here. You will find capabilities to create coding tasks, manage sessions, query statuses, and schedule recurring tasks.

## Security considerations

Protect your Jules API key by not committing it to version control. Use environment variables or a secrets manager. Optionally restrict repo access with an allowlist to prevent modifications to sensitive projects.

## Troubleshooting

If you encounter issues starting the server, verify that the environment variable JULES\_API\_KEY is set and that the local schedules file exists and is writable.

## Development notes

The project includes a TypeScript codebase with sources for types, storage, scheduling, MCP protocol, and a main entry point. Build commands are provided to compile, run, and type-check.

## Available tools

### create\_coding\_task

Creates an immediate Jules coding session by providing a natural language task prompt and a target repository, with optional branch and PR auto-creation.

### manage\_session

Manage active sessions to approve plans or send messages back to Jules for feedback.

### get\_session\_status

Query the status of an active Jules session to determine current progress and next steps.

### schedule\_recurring\_task

Schedule a task to run on a cron schedule, with prompt, source repository, and optional settings like time zone and PR behavior.

### list\_schedules

List all active schedules along with their next run times and history.

### delete\_schedule

Remove a scheduled task by its identifier.