MCP-server Discord Webhook

Created By
shehdrbs123a year ago
Model Context Protocol server for sending messages via Discord webhooks
Overview

What is MCP-server Discord Webhook?

MCP-server Discord Webhook is a module that allows real-time notifications to be sent to Discord channels from an MCP server.

How to use MCP-server Discord Webhook?

To use this module, you need to set up a Discord webhook URL and configure the MCP server to send messages through it. Follow the installation steps provided in the documentation.

Key features of MCP-server Discord Webhook?

  • Real-time Discord notifications via MCP server
  • Support for custom event messages
  • Easy setup and integration with existing systems

Use cases of MCP-server Discord Webhook?

  1. Sending alerts for server events to a Discord channel.
  2. Notifying users about important updates or changes in real-time.
  3. Integrating with other applications to provide instant feedback in Discord.

FAQ from MCP-server Discord Webhook?

  • What programming language is used for this module?

The module is developed in JavaScript and requires Node.js to run.

  • Is there a license for this module?

No, this module is free to use without any licensing restrictions.

  • How can I customize the messages sent to Discord?

You can customize the event messages in the MCP configuration settings.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
shehdrbs123
Star
0
Language
JavaScript
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago
Crevio

2 days ago