Skip to main content
Glama
baho0

capture-and-slack-mcp

by baho0
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to capture-and-slack-mcp

No user-submitted related servers found.

    Related Servers

    • screenshot-mcp

      937327493
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to capture screenshots of windows (e.g., WeChat developer tools) and save them locally, allowing the agent to read the image directly and close the code-change-to-review loop without OSS or network.
      1
      -

    • agent-wire

      grknbyk
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI coding agents to communicate with each other through a shared Slack channel, with signed messages, an auditable transcript, and human oversight.
      41 npm
      MIT

    • claude-slack-channel

      elys0912
      A
      license
      Not graded
      quality
      B
      maintenance
      Relays Slack direct messages into a locally running Claude Code session over MCP, so users can talk to their local agent from Slack. Replies, reactions, and execution-permission approvals (buttons or yes/no replies) are all handled inside Slack without opening ports or tunnels.
      10 npm
      MIT

    • redpen

      Benzenp
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables coding agents to capture pixel-accurate screenshots and DOM state from localhost apps, receive user-drawn instructions and reference images, and manage implementation review cycles.
      16 npm
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A4.4/5.0

    Scored across 7 tools

    Disambiguation5/5

    Each tool has a clear, distinct purpose: capture without posting, capture and post, send existing files, ask questions, check status, and two blocking wait variants. No two tools overlap in functionality.

    Naming Consistency5/5

    All tool names use snake_case with a consistent verb_noun pattern (ask_review, capture_window, check_review, send_to_slack, wait_for_reply, wait_for_review). The slightly longer 'capture_window_and_post' still follows the same structure and is clear.

    Tool Count5/5

    With 7 tools, the server is well-scoped for its purpose: capturing screenshots and managing Slack review workflows. Each tool adds necessary functionality without bloat or redundancy.

    Completeness4/5

    The tool set covers the main workflow: capture, post, review, follow-up. A minor gap is the lack of a tool to post a regular Slack message without a review, but the core review-focused flow is well-supported.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources