Skip to main content
Glama
650,501 tools. Updated 2026-10-13 23:36

"Zsh" matching MCP tools:

  • Start a persistent named terminal session for long-running work like dev servers or builds, then poll its output and stop it when done.
    Academic Free v1.1
    Destructive
  • Deploys a micropage build to its public URL, making the changes visible to visitors. Requires explicit confirmation and returns publishing status for tracking.
    MIT
    Destructive
  • Permanently deletes a post, removing it from the live site if published. No undo; use unpublish_post to only take it offline.
    MIT
    Destructive
  • Check which micropage account the server uses (email, plan, session or token). Call when login, session, or plan errors appear, or to see the connected account.
    MIT
  • Compiles .page markup into a draft build for a project, allowing preview before publishing. Replaces the entire source each time.
    MIT
    Destructive

Matching MCP Servers

  • A
    license
    Not graded
    quality
    C
    maintenance
    A Zsh execution tool for Claude Code providing yield-based command execution, PTY mode for interactive programs, circuit breaker for timeout protection, and adaptive learning (A.L.A.N.) for retry detection and proactive insights.
    5
    MIT
  • A
    license
    A
    quality
    C
    maintenance
    A single-purpose MCP server that lets an AI assistant run commands over SSH on a fixed, pre-configured host only, with an explicit per-call confirmation gate before execution.
    1
    MIT

Matching MCP Connectors

  • I run shell commands on your private cloud environment (bash, sh, zsh)

  • Twitter/X, YouTube, Reddit, Google and more - 100+ endpoints in total. No account, no OAuth, no subscription. Pay per call in USDC, or top up once and spend one balance across all of them.

  • Check a micropage publish's build and deploy progress after publish_build or publish_post, returning deploy events, done status, and the live URL.
    MIT
  • Take a published post offline and return it to draft, so its page 404s while the content stays available to republish later.
    MIT
    Destructive
  • Start a new empty micropage project in your signed-in account and receive a starter .page file to adapt. Nothing is published until you save and publish on request.
    MIT
  • Upload an image to a micropage project's storage from a local path, public URL, or base64, returning the filename and markup to reference it in pages or posts.
    MIT
    Destructive
  • Retrieve a project's posts (blog posts and newsletter emails) newest first, or fetch one in full by slug to review before editing.
    MIT
  • List every micropage project in the signed-in account, returning IDs, domains, URLs, and build status so you can find the project value other tools need or identify a site by name.
    MIT
  • Create or update a blog post or newsletter email by slug: an existing slug is updated, a new one is saved as a draft. Read the post first, then pass all fields back.
    MIT
    Destructive
  • Preview what publishing a post will do and get the confirmation token required to publish. Check email list, subscriber count, published status, and send permission without sending.
    MIT
  • Read a micropage project's raw .page source, llms.txt, and uploaded filenames for an active or older build. Use before editing to modify and save back.
    MIT
  • List a micropage project's builds, newest first, to find a build to roll back to, see why a publish failed, or check if a publish is still running.
    MIT
  • List files in a micropage project to see which filenames you can reference in markup, check if an image is already uploaded, and monitor storage usage.
    MIT
  • Retrieve full project details: live and editor URLs, active and latest builds, failure reasons, and custom-domain status. Use it to check what is live before publishing.
    MIT
  • Resolve a stored project file's public URL from its filename to link uploaded images or use them where a bare filename fails, such as a post's hero image.
    MIT