F
licenseA
qualityD
maintenanceMCP server for Google Jules enabling LLMs to create coding sessions with automatic pull request creation from issues or custom prompts.
4
-
Jules MCP Server
by MikBin
Related Servers
Alternatives to Jules MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceMCP server that exposes Google Jules AI agent as tools, allowing local AI agents to list authorized repositories and delegate coding tasks to Jules, receiving session URLs for tracking.91MIT
- AlicenseNot gradedqualityDmaintenanceAn MCP server that enables users to manage Google's Jules AI coding agent sessions directly from MCP-compatible clients. It supports creating sessions, approving execution plans, and interacting with session activity to streamline autonomous coding workflows.5 npmMIT
- AlicenseNot gradedqualityAmaintenanceMCP server for batch-dispatching coding tasks to Google Jules in parallel, with YAML task definitions, plan approval, and optional LLM-based task planning. Integrates with Claude Code and OpenAI Codex CLI as a tool.28 npm4MIT
- AlicenseAqualityAmaintenanceUnofficial MCP server for Google's Jules AI coding agent that lets AI assistants create and manage asynchronous coding tasks through the Jules API v1alpha.2059 npm2MIT
- AlicenseNot gradedqualityBmaintenanceAn MCP server that coordinates AI coding agents with mobile notifications, enabling task queues, inter-agent messaging, session monitoring, and human-in-the-loop approvals.MIT
TDQS
A3.6/5.0
Scored across 16 tools
Disambiguation4/5
Most tools map to a distinct resource and action: session CRUD, activities, sources, PR extraction, and monitoring are clearly separated. The only mild ambiguity is among get_session, check_jules, and monitor_session, since all report session status, but their one-shot vs. lightweight vs. polling semantics are clear from the descriptions.
Naming Consistency4/5
The set consistently uses a jules_ prefix and snake_case verb_noun style, making the general pattern predictable. jules_check_jules and jules_wait deviate slightly from the verb_noun convention, and the duplicated 'Jules' in check_jules is awkward, but these are minor exceptions.
Tool Count4/5
16 tools is slightly above the ideal 3-15 range, but the count is justified by the server's scope: session lifecycle, activity inspection, source lookup, PR extraction, and a polling/monitoring utility all require distinct tools. There is no obvious filler or redundant bloat.
Completeness5/5
The tool set covers the full Jules session workflow: create, read, list, delete, archive, unarchive, communicate, approve plans, monitor, inspect activities, extract PRs, and resolve sources. The included wait and monitor utilities prevent dead ends when handling asynchronous sessions.