Skip to main content
Glama
nickgnd

Tmux MCP Server

by nickgnd

create-session

Create a new tmux session with a specified name to organize terminal workflows within the Tmux MCP Server environment.

Instructions

Create a new tmux session

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
nameYesName for the new tmux session

Implementation Reference

  • MCP tool handler for 'create-session': calls tmux.createSession(name), handles success/error responses with formatted text output.
    async ({ name }) => {
      try {
        const session = await tmux.createSession(name);
        return {
          content: [{
            type: "text",
            text: session
              ? `Session created: ${JSON.stringify(session, null, 2)}`
              : `Failed to create session: ${name}`
          }]
        };
      } catch (error) {
        return {
          content: [{
            type: "text",
            text: `Error creating session: ${error}`
          }],
          isError: true
        };
      }
    }
  • Input schema defining 'name' parameter as required string.
    {
      name: z.string().describe("Name for the new tmux session")
    },
  • src/index.ts:170-172 (registration)
    Registration of the 'create-session' tool using server.tool() with name, description, schema, and handler.
    server.tool(
      "create-session",
      "Create a new tmux session",
  • Core helper function that executes the tmux 'new-session' command and retrieves the created session details.
    export async function createSession(name: string): Promise<TmuxSession | null> {
      await executeTmux(`new-session -d -s "${name}"`);
      return findSessionByName(name);
    }
Behavior2/5

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

With no annotations provided, the description carries the full burden of behavioral disclosure. It states the action but doesn't describe what happens upon creation (e.g., does it attach to the session, what permissions are needed, is it persistent). For a mutation tool with zero annotation coverage, this is a significant gap in transparency.

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?

The description is a single, efficient sentence that directly states the tool's purpose without any wasted words. It's appropriately sized and front-loaded, making it easy to parse quickly.

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

Completeness2/5

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

Given this is a mutation tool with no annotations and no output schema, the description is incomplete. It doesn't explain what the tool returns, what happens on success/failure, or any side effects. For a tool that creates resources, more context is needed for effective use.

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?

The schema description coverage is 100%, with the single parameter 'name' fully documented in the schema. The description doesn't add any additional meaning beyond what the schema provides (e.g., naming conventions, restrictions), so it meets the baseline for high schema coverage.

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

Purpose4/5

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

The description clearly states the action ('create') and resource ('new tmux session'), making the purpose immediately understandable. However, it doesn't differentiate from sibling tools like 'create-window' or 'find-session' beyond the basic resource type, which prevents a perfect score.

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

Usage Guidelines2/5

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

No guidance is provided on when to use this tool versus alternatives like 'create-window' or 'find-session'. The description only states what it does, not when it's appropriate or what prerequisites might exist for creating a session.

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

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