Python MCP reference

tool MCPstable

`load_buffer`

load_buffer( content: string, logical_name?: string | null, socket_name?: string | null, )

tool [source]¶

Load text into a new agent-namespaced tmux paste buffer.

Each call allocates a fresh buffer name — two concurrent calls will land in distinct buffers even if they pass the same logical_name. Agents MUST use the returned buffer_name on subsequent paste/show/delete calls.

When to use this vs. paste_text: load_buffer is the stage-then-fire path — you get a handle back and can inspect via show_buffer, paste into multiple panes via paste_buffer, or hold the content for later. Use paste_text for a simple one-shot paste with no follow-up.

MCP request method: tools/call Send load_buffer as the tool name, with the arguments below.

Arguments#

content (string) #

The text to stage. Can be multi-line. Redacted in audit logs.
logical_name? = null (string | null) #

Short label for the buffer. Limited to [A-Za-z0-9_.-]{1,64} so the final name stays safe on the tmux command line. Empty or None uses "buf".
socket_name? = null (string | null) #

tmux socket name.

No other arguments are accepted.

Result#

Returns object

buffer_name (string) #

The actual tmux buffer name (with prefix and UUID nonce). Pass this back to paste_buffer/show_buffer/delete_buffer.
logical_name? = null (string | null) #

Optional logical name supplied by the caller, if any.

Annotations#

destructiveHint: true
idempotentHint: false
openWorldHint: true
readOnlyHint: false

Protocol data#

Use the complete advertised contract for validation and client integration.

Input schema

{
  "additionalProperties": false,
  "properties": {
    "content": {
      "description": "The text to stage. Can be multi-line. Redacted in audit logs.",
      "type": "string"
    },
    "logical_name": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "default": null,
      "description": "Short label for the buffer. Limited to\n``[A-Za-z0-9_.-]{1,64}`` so the final name stays safe on the\ntmux command line. Empty or ``None`` uses ``\"buf\"``."
    },
    "socket_name": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "default": null,
      "description": "tmux socket name."
    }
  },
  "required": [
    "content"
  ],
  "type": "object"
}

Output schema

{
  "description": "Handle returned by :func:`~libtmux_mcp.tools.buffer_tools.load_buffer`.\n\nAgent-created tmux paste buffers are namespaced with a per-call UUID\nto avoid collisions on the server-global buffer namespace when\nconcurrent agents (or parallel tool calls from a single agent) are\nstaging content. Callers must use the ``buffer_name`` this model\ncarries on subsequent\n:func:`~libtmux_mcp.tools.buffer_tools.paste_buffer`,\n:func:`~libtmux_mcp.tools.buffer_tools.show_buffer`, and\n:func:`~libtmux_mcp.tools.buffer_tools.delete_buffer` calls.",
  "properties": {
    "buffer_name": {
      "description": "The actual tmux buffer name (with prefix and UUID nonce). Pass this back to paste_buffer/show_buffer/delete_buffer.",
      "type": "string"
    },
    "logical_name": {
      "anyOf": [
        {
          "type": "string"
        },
        {
          "type": "null"
        }
      ],
      "default": null,
      "description": "Optional logical name supplied by the caller, if any."
    }
  },
  "required": [
    "buffer_name"
  ],
  "type": "object"
}

Scripting & web

Compiled & native

JVM

.NET

tmux

`load_buffer`

Arguments#

Result#

Annotations#

Protocol data#