Skip to main content
Glama

Related Servers

Alternatives to Nockit MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      A lightweight, stdio-based MCP server enabling AI assistants to perform local file system operations like reading, writing, searching, and executing commands.
      1,023 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A local MCP server that gives AI agents access to developer tooling — GitHub (read-only), documentation search, and web research — via stdio transport.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that gives your AI assistant full awareness of your local dev environment — running processes, Docker containers, git state, open ports, log files, and more.
      6 npm
      1
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      Production-grade MCP server that gives AI agents safe access to your local dev environment: filesystem, databases, processes, and OpenAPI specs.
      15
      23 npm
      3
      MIT
    • A
      license
      C
      quality
      F
      maintenance
      This MCP server gives an AI coding host controlled, client-agnostic access to a local machine's developer capabilities: transactional file edits, shell and PTY execution, Git and project inspection, language-server operations, isolated browser automation, Windows UI automation, VS Code state, durable jobs, and checkpoints, all bounded by filesystem root allowlisting and resource admission controls. It speaks standard MCP over stdio, Streamable HTTP, and legacy HTTP+SSE, and can also run headless as a long-lived job runner without any hosted model vendor.
      114
      ISC

    TDQS

    A4.9/5.0

    Scored across 1 tool

    Disambiguation5/5

    There is only one tool, so there is no possibility of confusing it with others. Its purpose is clear and specific.

    Naming Consistency5/5

    With a single tool, naming consistency is trivially maintained. The name 'send_push_notification' is descriptive and follows a standard verb_noun pattern.

    Tool Count4/5

    One tool is slightly below the typical 3-15 range, but the server's narrow purpose (push notifications) justifies this minimal surface. It is not overly thin because the tool covers all relevant statuses and includes a fallback.

    Completeness5/5

    For the domain of push notifications, the tool covers all necessary states (completed, needs_input, failed) and provides a one-line summary. There are no obvious missing operations for this singular purpose.

    Maintenance

    ActivityStale
    ResponsivenessNo issues