Skip to main content
Glama
PiMPStudios

claude-tmux-bridge

by PiMPStudios
OverviewSchemaRelated ServersScoreDiscussions
JavaScript
Local

Server Quality Checklist

67%
Profile completionA complete profile improves this server's visibility in search results.

  • Latest release: v2.3.0

  • Disambiguation5/5

    Only one tool exists, so there is no possibility of confusion between tools. The single tool's purpose is crystal clear.

    Naming Consistency5/5

    With only one tool, naming consistency is trivially maintained. The name 'claude_code' accurately reflects its function.

    Tool Count3/5

    One tool feels thin for a bridge server, but it does encapsulate the core operation. A more complete set might include session management tools.

    Completeness4/5

    The tool covers the primary use case of sending prompts and implicitly handles session startup. Minor gaps like explicit session listing or termination exist.

  • Average 4.4/5 across 1 of 1 tools scored.

    See the Tool Scores section below for per-tool breakdowns.

    • No community issues in the last 6 months
    • 0 commits in the last 12 weeks
    • No stable releases found
    • No critical vulnerability alerts
    • No high-severity vulnerability alerts
    • No code scanning findings
    • CI is passing

  • This repository is licensed under MIT License.

  • This repository includes a README.md file.

  • No tool usage detected in the last 30 days. Usage tracking helps demonstrate server value.

    Tip: use the "Try in Browser" feature on the server page to seed initial usage.

  • Add a glama.json file to provide metadata about your server.

  • If you are the author, simply .

    If the server belongs to an organization, first add glama.json to the root of your repository:

    {
  "$schema": "https://glama.ai/mcp/schemas/server.json",
  "maintainers": [
    "your-github-username"
  ]
}

    Then . Browse examples.

  • Add related servers to improve discoverability.

How to sync the server with GitHub?

Servers are automatically synced at least once per day, but you can also sync manually at any time to instantly update the server profile.

To manually sync the server, click the "Sync Server" button in the MCP server admin interface.

How is the quality score calculated?

The overall quality score combines two components: Tool Definition Quality (70%) and Server Coherence (30%).

Tool Definition Quality measures how well each tool describes itself to AI agents. Every tool is scored 1–5 across six dimensions: Purpose Clarity (25%), Usage Guidelines (20%), Behavioral Transparency (20%), Parameter Semantics (15%), Conciseness & Structure (10%), and Contextual Completeness (10%). The server-level definition quality score is calculated as 60% mean TDQS + 40% minimum TDQS, so a single poorly described tool pulls the score down.

Server Coherence evaluates how well the tools work together as a set, scoring four dimensions equally: Disambiguation (can agents tell tools apart?), Naming Consistency, Tool Count Appropriateness, and Completeness (are there gaps in the tool surface?).

Tiers are derived from the overall score: A (≥3.5), B (≥3.0), C (≥2.0), D (≥1.0), F (<1.0). B and above is considered passing.

Tool Scores

  • Behavior5/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 excels: auto-start behavior, busy error on concurrent calls, full conversation history preservation, MCP tool access, and session naming rules are all clearly disclosed. This gives the agent a robust understanding of side effects and constraints.

    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 well-organized with clear sections (SESSION NAMING, BEHAVIOUR) and bullet points. Each sentence carries useful information without redundancy. It is appropriately sized for the tool's complexity, front-loading the core purpose, and every line earns its place.

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

    Completeness4/5

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

    The description covers a wide range of context: session naming, auto-start, concurrency, history, and MCP access. However, it does not specify the return value shape (e.g., whether it returns the full Claude response or just a status), which would be valuable given the absence of an output schema. This is a minor gap in an otherwise thorough description.

    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?

    Schema coverage is 100%, so the schema itself already documents all parameters in detail, including use cases for compact and clearContext. The main description adds only session naming context, which is also present in the workFolder parameter description. The description provides no significant semantic value beyond what the schema offers, matching the baseline.

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

    Purpose5/5

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

    The description opens with a specific verb+resource statement: 'Send a prompt to an interactive Claude Code session running in a tmux terminal.' It clearly identifies the tool's function and scope. Even without siblings to distinguish from, the purpose is unambiguous and detailed.

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

    Usage Guidelines4/5

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

    The description provides clear context on when the tool should be used, including automatic session creation and the concurrency limitation. It doesn't explicitly name alternatives (no sibling tools exist), but parameter descriptions for compact and clearContext offer strong usage guidance for choosing between them, effectively covering the when/when-not aspect.

    Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

GitHub Badge

Glama performs regular codebase and documentation scans to:

  • Confirm that the MCP server is working as expected.
  • Confirm that there are no obvious security issues.
  • Evaluate tool definition quality.

Our badge communicates server capabilities, safety, and installation instructions.

Card Badge

claude-tmux-bridge MCP server

Copy to your README.md:

Score Badge

claude-tmux-bridge MCP server

Copy to your README.md:

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/PiMPStudios/claude-tmux-bridge'

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