zellij-mcp-server

Created By
superpositiona year ago
A MCP Server to over zellij over STDIO
Overview

what is zellij-mcp-server?

zellij-mcp-server is a Multi-Channel Protocol (MCP) server designed to work with Zellij, a terminal workspace. It facilitates communication over standard input/output (STDIO).

how to use zellij-mcp-server?

To use zellij-mcp-server, you need to set it up in your terminal environment and connect it with Zellij to manage multiple terminal sessions efficiently.

key features of zellij-mcp-server?

  • Supports Multi-Channel Protocol for terminal communication
  • Integrates seamlessly with Zellij for enhanced terminal management
  • Allows for efficient handling of multiple terminal sessions over STDIO

use cases of zellij-mcp-server?

  1. Managing multiple terminal sessions in a single workspace.
  2. Enhancing productivity by organizing terminal commands and outputs.
  3. Facilitating communication between different terminal applications.

FAQ from zellij-mcp-server?

  • What is the purpose of zellij-mcp-server?

It serves as a server to manage multiple terminal sessions using the Multi-Channel Protocol.

  • Is zellij-mcp-server free to use?

Yes! It is open-source and available for anyone to use.

  • How can I contribute to zellij-mcp-server?

You can contribute by visiting the GitHub repository and submitting pull requests or reporting issues.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
superposition
Star
0
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago
Tavily Mcp
@tavily-ai

JavaScript
a year ago