Skip to main content
Glama
freelancernasimofficial

nascoder-terminal-browser-mcp

by freelancernasimofficial
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to nascoder-terminal-browser-mcp

No user-submitted related servers found.

    Related Servers

    • webpilot

      luckysolanki902
      A
      license
      Not graded
      quality
      C
      maintenance
      A semantic terminal browser that renders web pages as structured numbered elements for LLM agents via MCP, enabling agents to navigate, interact, and extract data from any website.
      8 npm
      MIT

    • kage-mcp

      lxyct825-ops
      A
      license
      Not graded
      quality
      C
      maintenance
      A lightweight MCP server for parsing HTML, fetching URLs, rendering terminal-style screenshots, and executing JavaScript on static HTML without external dependencies.
      3
      MIT

    • cdpilot

      mehmetnadir
      A
      license
      Not graded
      quality
      A
      maintenance
      Zero-dependency browser automation CLI with 40+ commands. Navigate, click, fill forms, take screenshots, capture network traffic, and more — all via Chrome DevTools Protocol. Built-in accessibility tree snapshots for AI agents (500x fewer tokens than screenshot-based approaches). Works with any Chromium browser already installed. 50KB total, no Playwright or Puppeteer needed.
      49 npm
      31
      MIT

    • ai-browser

      void-builder-1
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to fully control a terminal browser via MCP, navigating pages, filling forms, logging in, and managing cookies with deterministic numbered links and forms. Also provides an interactive human CLI.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.1/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clear, distinct purpose: browsing, checking available browsers, and extracting links. No overlap or ambiguity between them.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (terminal_browse, check_browsers, extract_links), making the set predictable and easy to navigate.

    Tool Count5/5

    With only 3 tools, the server is tightly scoped to terminal browsing. Each tool is essential and there is no bloat or redundancy.

    Completeness5/5

    The tool surface fully covers the stated domain: browsing content, checking browser availability, and extracting links. There are no obvious gaps for typical terminal browsing workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources