Schema | shell-use

shell-use

Describes the environment variables required to run the server.

Name	Required	Description	Default
`SHELL_USE_SOCKET`	No	Path to tmux socket (default: /tmux/tmux.sock in Docker)
`SHELL_USE_SESSIONS`	Yes	Comma-separated list of allowed session names

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.

Features and capabilities supported by this server

Protocol revision2025-11-25

Capability	Details
`tools`	{ "listChanged": false }
`prompts`	{ "listChanged": false }
`resources`	{ "subscribe": false, "listChanged": false }
`experimental`	{}

Functions exposed to the LLM to take actions

Name	Description
list_sessionsA	Returns list of available tmux sessions.
captureC	Captures current terminal screen text.
send_keysC	Sends key input. Supports tmux key notation (Enter, C-c, etc.).
send_textA	Sends literal text via tmux buffer. Supports multiline text with \n and \t. Use enter=True for shell commands - automatically presses Enter after sending. Use enter=False (default) for editors - newlines are preserved as text. Examples: - Shell: send_text(session, "ls -la", enter=True) -> executes command - Editor: send_text(session, "line1\nline2") -> pastes two lines
scrollA	Navigates the scrollback buffer (half-pages by default).
exit_scroll_modeA	Exits tmux copy-mode and returns to normal mode.

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

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

curl -X GET 'https://glama.ai/api/mcp/v1/servers/kyuheon-kr/shell-use'

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