Jules MCP Server
Exposes Google Jules AI capabilities for automated coding tasks, including session management, code reviews, and unified diff handling. It enables users to create sessions, approve plans, and synchronize AI-generated code changes with GitHub repositories.
README
Jules MCP Server
MCP server that exposes Google Jules capabilities using @google/jules-sdk. This unified implementation uses the SDK plus direct API calls where needed, while keeping SDK-backed caching, snapshots, and artifact handling. MCP tools may use either the SDK or the REST API, whichever is the best fit for the specific operation.
Setup
- Install dependencies
- Provide
JULES_API_KEYvia environment or~/.jules/config.json - Build the server
npm install
npm run build
Run locally:
JULES_API_KEY=your_api_key node dist/cli.js
OpenCode Integration
This repo includes a project-level OpenCode config at .opencode/opencode.json. For global setup, add to ~/.config/opencode/opencode.json (update the command path to where you built this server):
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"jules": {
"type": "local",
"command": ["node", "/path/to/your/jules-mcp/dist/cli.js"],
"environment": {
"JULES_API_KEY": "your_api_key"
}
}
}
}
Antigravity Integration
Example OpenCode plugin enablement snippet (merge into your config):
{
"$schema": "https://opencode.ai/config.json",
"plugins": {
"opencode-antigravity-auth": {
"enabled": true
}
}
}
Tools
SDK Tools
| Tool | Purpose | Key Params | Returns |
|---|---|---|---|
create_session |
Create a new Jules session or automated run (supports repoless sessions). | prompt (req)<br>repo<br>branch<br>interactive<br>autoPr |
Session created. ID: <sessionId> |
list_sessions |
List recent sessions with pagination. | pageSize<br>pageToken |
{ sessions: [...], nextPageToken? } |
get_session_state |
Session dashboard (status, last activity/message, pending plan). | sessionId (req) |
Status object with activity/message/plan context |
send_reply_to_session |
Approve plan, send a message, or ask and wait for a reply. | sessionId (req)<br>action (approve/send/ask)<br>message (send/ask) |
Confirmation or agent reply |
get_code_review_context |
Summarize code changes with file list and metadata. | sessionId (req)<br>activityId<br>format<br>filter<br>detail |
Formatted summary string |
show_code_diff |
Get the unified diff for a session or file. | sessionId (req)<br>file<br>activityId |
Unified diff text |
query_cache |
Query the local cache using JQL. | query (req) |
{ results: [...], _meta? } |
Query example:
{
"query": {
"from": "sessions",
"where": { "state": "failed" },
"limit": 5
}
}
Additional Tools (jules_*)
These tools are part of the same unified server and expose REST-style workflows plus convenience operations. They may use the SDK or the REST API under the hood, depending on which path is required for the operation. They return a structured ToolResult object:
{ success, message, data?, error?, suggestedNextSteps? }
| Tool | Purpose | Key Params | Notes |
|---|---|---|---|
jules_list_sources |
List connected repositories. | pageSize<br>pageToken |
Returns { sources, hasMore, nextPageToken } |
jules_get_source |
Get details for a connected repository. | source (req) |
Accepts sources/github/owner/repo or owner/repo |
jules_create_session |
Create a session with automation settings. | prompt (req)<br>repo (req)<br>branch<br>title<br>automationMode<br>requirePlanApproval |
Draft PR falls back to AUTO_CREATE_PR if not supported |
jules_get_session |
Get session status/details. | sessionId (req) |
— |
jules_list_sessions |
List sessions with pagination. | pageSize<br>pageToken |
— |
jules_approve_plan |
Approve a pending plan. | sessionId (req) |
— |
jules_reject_plan |
Reject a plan with feedback. | sessionId (req)<br>feedback |
Uses REST endpoint |
jules_send_message |
Send a message to a session. | sessionId (req)<br>message (req) |
— |
jules_cancel_session |
Cancel a running session. | sessionId (req) |
Uses REST endpoint |
jules_list_activities |
List activities in a session. | sessionId (req)<br>pageSize<br>pageToken |
— |
jules_get_latest_activity |
Get most recent activity. | sessionId (req) |
— |
jules_get_session_plan |
Get latest plan (if generated). | sessionId (req) |
Plan rejection detection uses REST activity listing |
jules_wait_for_completion |
Wait for completion or timeout. | sessionId (req)<br>timeoutMs<br>pollIntervalMs |
— |
jules_wait_for_plan |
Wait for plan generation. | sessionId (req)<br>timeoutMs |
— |
jules_create_and_wait |
Create and optionally wait for completion. | prompt (req)<br>repo (req)<br>branch<br>title<br>automationMode<br>waitForCompletion<br>timeoutMs<br>requirePlanApproval |
Draft PR falls back to AUTO_CREATE_PR if not supported |
jules_quick_task |
Create session with defaults and wait. | prompt (req)<br>repo (req)<br>branch<br>createPr |
— |
jules_get_session_summary |
Combined session + activity summary. | sessionId (req) |
— |
jules_sync_local_codebase |
Apply Jules diff to a local git repo. | sessionId (req)<br>repoPath<br>activityId<br>file<br>dryRun<br>allowDirty<br>autoStash<br>threeWay |
Refuses dirty trees by default unless allowDirty=true or autoStash=true |
Hidden Tool (Not Listed in MCP)
| Tool | Purpose | Key Params | Notes |
|---|---|---|---|
get_bash_outputs |
Get bash command outputs from a session. | sessionId (req)<br>activityIds |
Not listed in MCP discovery |
Behavior Notes
AUTO_CREATE_DRAFT_PRis not supported by the SDK. When requested forjules_create_sessionorjules_create_and_wait, the server retries withAUTO_CREATE_PR.jules_reject_planandjules_cancel_sessionuse direct REST endpoints when the SDK does not expose public helpers.- Plan rejection status depends on a
planRejectedactivity; if the API does not emit it, the status remainspending_approval. jules_sync_local_codebaseapplies patches viagit applyand refuses dirty working trees unlessallowDirty=trueorautoStash=true.
Configuration
The server reads configuration from:
JULES_API_KEYenv var or~/.jules/config.json- Optional overrides:
JULES_API_BASE_URLJULES_API_TIMEOUTorJULES_REQUEST_TIMEOUT_MSJULES_POLL_INTERVALJULES_RATE_LIMIT_MAX_RETRY_MSJULES_RATE_LIMIT_BASE_DELAY_MSJULES_RATE_LIMIT_MAX_DELAY_MS
CLI
The CLI supports doctor and config commands (like the official SDK MCP):
# Check environment and API connectivity
jules-mcp-server doctor
# Save API key to ~/.jules/config.json
jules-mcp-server config --key YOUR_KEY
Credits
Special thanks to David East for building the SDK and API on which this MCP is based.
推荐服务器
Baidu Map
百度地图核心API现已全面兼容MCP协议,是国内首家兼容MCP协议的地图服务商。
Playwright MCP Server
一个模型上下文协议服务器,它使大型语言模型能够通过结构化的可访问性快照与网页进行交互,而无需视觉模型或屏幕截图。
Magic Component Platform (MCP)
一个由人工智能驱动的工具,可以从自然语言描述生成现代化的用户界面组件,并与流行的集成开发环境(IDE)集成,从而简化用户界面开发流程。
Audiense Insights MCP Server
通过模型上下文协议启用与 Audiense Insights 账户的交互,从而促进营销洞察和受众数据的提取和分析,包括人口统计信息、行为和影响者互动。
VeyraX
一个单一的 MCP 工具,连接你所有喜爱的工具:Gmail、日历以及其他 40 多个工具。
graphlit-mcp-server
模型上下文协议 (MCP) 服务器实现了 MCP 客户端与 Graphlit 服务之间的集成。 除了网络爬取之外,还可以将任何内容(从 Slack 到 Gmail 再到播客订阅源)导入到 Graphlit 项目中,然后从 MCP 客户端检索相关内容。
Kagi MCP Server
一个 MCP 服务器,集成了 Kagi 搜索功能和 Claude AI,使 Claude 能够在回答需要最新信息的问题时执行实时网络搜索。
e2b-mcp-server
使用 MCP 通过 e2b 运行代码。
Neon MCP Server
用于与 Neon 管理 API 和数据库交互的 MCP 服务器
Exa MCP Server
模型上下文协议(MCP)服务器允许像 Claude 这样的 AI 助手使用 Exa AI 搜索 API 进行网络搜索。这种设置允许 AI 模型以安全和受控的方式获取实时的网络信息。