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
Payai X402 Tools

6 hours ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

a day ago