Skip to main content
Glama
Maaa2005

wcc

by Maaa2005
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to wcc

No user-submitted related servers found.

    Related Servers

    • webnav

      lucyfuur94
      A
      license
      Not graded
      quality
      A
      maintenance
      webnav is an MCP server that gives web-browsing AI agents a reusable, deterministic site map, so they stop re-exploring sites every run. It enables page-to-page navigation with zero LLM overhead, pausing only at genuine decision points.
      36 npm
      Apache 2.0

    • krwl3r

      garciarsdiego
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for web scraping and browser automation, enabling AI agents to extract clean, token-efficient content from web pages.
      1
      MIT

    • ApiTap

      n1byn1kt
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server that turns any website into an API by capturing or importing API endpoints, enabling AI agents to interact with web services without a browser, with 20-100x token cost reduction versus browser automation.
      99 npm
      125
      Apache 2.0

    • helmdeck

      tosin2013
      A
      license
      Not graded
      quality
      B
      maintenance
      A self-hosted MCP server that provides capability packs for AI agents to perform browser, desktop, git, and code actions via schema-validated JSON calls, enabling reliable agentic workflows even with small open-weight models.
      4
      Apache 2.0

    • Oktyv

      duke-of-beans
      F
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that enables AI agents to execute real-world actions through 10 specialized engines covering authenticated API calls, browser automation, visual QA, shell commands, file operations, job scraping, and parallel task execution.
      -
    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 6 tools

    Disambiguation5/5

    Each tool has a distinct role in the session lifecycle: opening, inspecting, listing, executing, retrieving results, and closing. There is no overlap in purpose; even get_execution_result and execute_capability differ in that one runs a capability and the other fetches a stored result.

    Naming Consistency5/5

    All tool names follow the same verb_noun snake_case pattern (open_session, inspect_page, list_capabilities, etc.). The verbs are clear and the nouns correspond to the domain entities, making the set highly predictable.

    Tool Count5/5

    With 6 tools, the server is well-scoped for its purpose of session-based browser automation. Each tool is necessary and covers a distinct step in the workflow, neither too few nor too many.

    Completeness4/5

    The lifecycle from opening a session through inspection, capability execution, result retrieval, and closing is fully covered. The only notable gap is the lack of an explicit navigation tool to change the URL within an open session, though capabilities may inherently handle page changes.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources