Schema | oracle-tmux-mcp

oracle-tmux-mcp

Describes the environment variables required to run the server.

Name	Required	Description	Default
No arguments

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": true }

Functions exposed to the LLM to take actions

Name	Description
tmux_register_agentB	Register an agent and ensure its live tmux pane exists. Not required before send/broadcast — they self-provision — but useful to pre-create a pane before anyone messages that agent.
tmux_sendB	Send a message to one agent. Appears instantly in the recipient's tmux pane (push-based, no polling) and is recorded in their queryable history.
tmux_broadcastC	Send a message to every registered agent (except the sender). Each recipient's pane updates instantly.
tmux_list_agentsA	List every agent registered in the mesh.
tmux_historyA	Fetch an agent's structured message history (source of truth — the tmux pane is just a live view of the same data).
tmux_open_claudeA	Spawn an interactive Claude Code session in a tmux pane as the given agent. From then on, tmux_send to that agent types the message directly into that chat — it appears on screen and Claude responds, no polling and no human input.
tmux_attach_infoA	Get the shell command a human can run to attach a terminal directly to one agent's live pane.

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/JonusNattapong/oracle-tmux-mcp'

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