Skip to main content
Glama
Sign In
nu11b1ade

ARTEX Web MCP

by nu11b1ade
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to ARTEX Web MCP

No user-submitted related servers found.

    Related Servers

    • agenzax-mcp

      Agenzax
      A
      license
      A
      quality
      B
      maintenance
      Enables MCP clients to connect to Agenzax's REST API over stdio, providing tools for messaging, session management, and review-mode oversight.
      18
      42 npm
      5
      MIT

    • mcp-pc-connector

      PourrezJ
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables a remote AI client to work on a PC over Streamable HTTP: reading files, viewing images, applying patches (Codex or unified diff), running one-shot or interactive shell commands, and writing to stdin sessions. It also acts as a gateway that exposes local stdio MCP servers, such as Blender, under namespaced tool names like blender__execute_blender_code.
      MIT

    • MCP HTTP Proxy

      PintaAI
      A
      license
      Not graded
      quality
      D
      maintenance
      Exposes any stdio-based MCP server to the internet via HTTP/SSE transport, enabling remote agents to access MCP tools over a network.
      8 npm
      MIT
    Deploy Server
    Let your AI agent see the webWeb-to-screenshot MCP for Claude, Cursor and Codex. No cookie banners. Free to start.snap-render.comAd

    TDQS

    B3.3/5.0

    Scored across 10 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes: route invocation (artex_call), discovery (artex_find_routes), event streaming (artex_read_events), browser automation (artex_browser), and status. The only mild overlaps are artex_initialize vs artex_login (both establish a session) and artex_change_password vs artex_configure_basic_auth (both rotate credentials), but the descriptions make the distinction between first-run setup, normal login, app password, and HTTP Basic gate explicit.

    Naming Consistency4/5

    All ten tools share a consistent artex_ prefix and snake_case, and most use a verb_noun shape (find_routes, read_events, change_password, configure_basic_auth). Minor deviations are noun-only names (artex_browser, artex_status) and bare verbs (artex_call, artex_login), but the pattern remains predictable.

    Tool Count5/5

    Ten tools is well within the ideal range and each earns its place: session lifecycle, credential rotation, route discovery/invocation, event streaming, browser automation, and health check. There is no filler or redundant surface for what is essentially a generic web gateway.

    Completeness4/5

    The surface covers the full session and credential lifecycle (initialize, login, logout, change password, basic-auth config) plus discovery, invocation, streaming, and browser inspection, so an agent is unlikely to hit a dead end. Minor gaps remain: no explicit route-listing beyond search terms, and no direct tooling for managing files in the transfer directory (only referenced indirectly via save_as/upload_files).

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources