Skip to main content
Glama
dfsf2151

salla-custom-code-mcp

by dfsf2151
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to salla-custom-code-mcp

No user-submitted related servers found.

    Related Servers

    • js-reverse-mcp

      zhangjia2024
      A
      license
      A
      quality
      B
      maintenance
      Enables AI coding assistants to debug and analyze JavaScript in web pages by managing scripts, breakpoints, network and WebSocket traffic, browser state, and local file inputs/outputs for continuous reverse-engineering workflows.
      24
      6,479 npm
      Apache 2.0

    • chrome-driverless

      friddle
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables browser automation through a persistent Chrome instance exposed via HTTP, including navigation, screenshots, clicks, typing, multi-tab and multi-profile management, proxy switching, login state export, and AI-driven task execution.
      -

    • dev-chrome-monitor

      2sslgetlool
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables interaction with Chromium browser instances through Puppeteer for inspecting dev builds, capturing screenshots, and automating UI interactions. Features permission-gated tools for secure browser navigation, DOM manipulation, and JavaScript evaluation.
      11 npm
      1
      MIT

    • KDP Studio MCP

      fatoh2
      F
      license
      B
      quality
      C
      maintenance
      Enables reading KDP paperback drafts and making a single guarded cover-finish change through a user-authorized, already signed-in Chrome session while keeping credentials and tokens in the browser.
      3
      -
    Deploy Server
    Give agents eyes on the webHosted screenshot MCP. Send a URL, get a pixel-perfect image. $0.002 per grab. Works with Claude, Cursor, and Codex.grabbit.liveAd

    TDQS

    A3.9/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool targets a clearly distinct resource and action: CSS read/update, JS read/update, and JS enable/disable. There is no meaningful overlap between custom_css_update and custom_js_toggle or any other pair.

    Naming Consistency5/5

    All tools follow the same snake_case pattern custom_{css|js}_{get|update|toggle}. The convention is predictable and easy to map to the underlying resources.

    Tool Count5/5

    Five tools is well-scoped for managing custom CSS and JavaScript. Each tool earns its place by covering a distinct operation without unnecessary surface area.

    Completeness4/5

    The surface covers reading and replacing both CSS and JS, plus toggling JS, which is the core workflow. Minor gaps exist around backup/restore visibility or an explicit reset operation, but agents can work around them by passing empty or full content.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources