Skip to main content
Glama
nayagamez

claude-cli-mcp

by nayagamez
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault
CLAUDE_CLI_PATHNoPath to the Claude Code CLI binaryclaude
CLAUDE_MCP_DEBUGNoSet to enable debug logging to stderr
CLAUDE_TIMEOUT_MSNoIdle timeout for child Claude process600000

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

CapabilityDetails
tools
{
  "listChanged": true
}

Tools

Functions exposed to the LLM to take actions

NameDescription
claudeA

Run a Claude Code CLI session. Executes claude -p --output-format stream-json as a subprocess and returns the result.

Use this tool to start a new coding task with Claude Code. The response includes a Session ID that can be used with the claude-reply tool to continue the conversation.

WARNING: defaults to permission mode bypassPermissions (parity with codex --full-auto). Use a safer mode (e.g. acceptEdits or auto) for sensitive workspaces.

claude-replyA

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.

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.2/5.0

Scored across 2 tools

Disambiguation5/5

The two tools have clearly distinct purposes: 'claude' starts a new Claude Code CLI session, while 'claude-reply' continues an existing session using a session ID. There is no overlap or ambiguity.

Naming Consistency5/5

Both tool names use a consistent lowercase-with-hyphen pattern ('claude' and 'claude-reply'), where the first is a base command and the second adds a modifier. The naming is predictable and clear.

Tool Count4/5

With only two tools, the set is minimal but sufficient for starting and continuing Claude Code sessions. The count is slightly low but reasonable given the focused scope of the server.

Completeness3/5

The server covers the essential actions (starting and continuing sessions) but lacks tools for explicitly ending sessions, listing active sessions, or changing session parameters. The absence of session management creates a notable gap.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources