gemini-cli-mcp-async
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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 |
|---|---|
| gemini_cli_executeB | Execute Gemini CLI synchronously with configurable parameters. Supports both interactive and non-interactive prompts. |
| gemini_cli_execute_asyncA | Start a Gemini CLI task in the background and return immediately with a task_id. Use gemini_cli_check_result to retrieve the result. |
| gemini_cli_check_resultB | Check the status of an async Gemini CLI task. Returns running/completed status and the result if available. |
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
The three tools are clearly distinct: synchronous execution, asynchronous task start, and result checking. The descriptions reinforce the differences, leaving no meaningful overlap.
All tools share the gemini_cli_ prefix and follow a consistent snake_case verb_noun pattern: execute, execute_async, check_result. Naming is predictable and uniform.
Three tools is an appropriate minimal set for a focused async execution wrapper. Each tool serves a necessary and non-redundant role.
The core workflow of sync execution, async launch, and result retrieval is covered. Cancellation or task listing is not provided, but the basic async lifecycle is complete enough for most use cases.