Skip to main content
Glama
nayagamez

claude-cli-mcp

by nayagamez
OverviewSchemaRelated ServersScoreDiscussions
TypeScript
Local

claude-reply

Resume a previous Claude Code CLI session by supplying a session ID and a follow-up prompt to continue the conversation from where it left off.

Instructions

Continue a Claude Code CLI conversation by providing the session ID from a previous claude call and a follow-up prompt.

Uses claude --resume <session-id> to load the previous session and continue.

NOTE: Sessions are tied to the directory they were started in (Claude Code issue #5768). The MCP server cannot change the resumed session's working directory — make sure the host process runs from the original cwd, otherwise the session may not be found.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
promptYesThe follow-up prompt to send to Claude
sessionIdYesThe session ID from a previous claude tool call
modelNoModel id or alias. Do NOT set unless the user explicitly requests one.
effortNoReasoning effort. Auto-select based on task complexity.
permissionModeNoPermission mode. Whether resume honors mid-session changes is experimental — see plan §6.5.
allowedToolsNoTools Claude may use without permission prompt (e.g. ["Bash(git *)", "Edit"]).
disallowedToolsNoTools Claude must not use.
appendSystemPromptNoText appended to the default system prompt.
mcpConfigNoMCP server config files or JSON strings (--mcp-config, repeatable).
maxTurnsNoLimit the number of agentic turns (--max-turns).
forkSessionNoCreate a new session ID instead of reusing the original (--fork-session).
bareNoRun with --bare. Requires ANTHROPIC_API_KEY or apiKeyHelper.
timeoutNoIdle timeout in milliseconds (default: 600000 = 10 min).

Tool Definition Quality

A4/5.0
Behavior3/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

Discloses the underlying mechanism (claude --resume) and a known issue (directory dependency). However, lacks details on error handling, return behavior, or consequences of invalid session IDs. Relies on schema for parameter descriptions.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Two short paragraphs with no redundant information. First sentence clearly states the tool's purpose, followed by mechanism and a necessary caveat. Efficient and front-loaded.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness4/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

For a tool with 13 parameters and no output schema, the description provides essential context on usage and a critical limitation. Could include more on return values or error states, but the caveat about directory binding is valuable for correct invocation.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema describes all 13 parameters with 100% coverage, so baseline is 3. The description adds context about session ID directory binding but does not significantly enhance parameter understanding beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

Clearly states it continues a Claude Code CLI conversation using a session ID and follow-up prompt. Distinguishes itself from the sibling 'claude' tool by specifying resumption rather than initiation.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

Provides context on when to use (follow-up conversations) and includes a critical caveat about directory binding. Could explicitly exclude use for new conversations, but the distinction from 'claude' is implied.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/nayagamez/claude-cli-mcp'

If you have feedback or need assistance with the MCP directory API, please join our Discord server