Cicall
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CICALL_HOME | No | Runtime state directory | ~/.local/state/cicall |
| CICALL_SOCKET | No | Unix socket path | $CICALL_HOME/cicall.sock |
| CICALL_PROJECT | No | Default MCP project scope | current directory name |
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 |
|---|---|
| list_sessionsA | List CLI sessions in this Cicall project. |
| read_outputC | Read the recent output of a managed CLI session. |
| send_textB | Type text into a session. Set submit=true to append Enter. |
| send_keyC | Send a special key such as enter, escape, arrows, or ctrl-c. |
| start_sessionB | Start any CLI program in a managed PTY in this project. cwd defaults to the MCP server's configured working directory. Returns only the new session id for easy follow-up calls. |
| close_sessionC | Terminate a managed CLI session in this project. |
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 6 tools
Each tool targets a distinct operation on CLI sessions: starting, closing, listing, sending text, sending keys, and reading output. No overlap in functionality.
All tools follow a consistent verb_noun pattern (e.g., start_session, close_session, list_sessions, send_text, send_key, read_output).
With 6 tools, the set is well-scoped for managing CLI sessions. Each tool serves a necessary role without excess or insufficiency.
The tools cover the full lifecycle of a CLI session: creation, interaction (text, keys, output reading), and destruction, plus listing. No obvious gaps for the intended domain.