MCP Server Discord Webhook

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is MCP Server Discord Webhook?

MCP Server Discord Webhook is a tool that allows users to post messages to Discord webhooks from an MCP server.

how to use MCP Server Discord Webhook?

To use the MCP Server Discord Webhook, install it via npm and configure it in your MCP configuration file with your Discord webhook URL.

key features of MCP Server Discord Webhook?

  • Sends messages to Discord channels via webhooks.
  • Customizable display name and avatar for messages.
  • Easy integration with MCP servers.

use cases of MCP Server Discord Webhook?

  1. Sending automated notifications to a Discord channel.
  2. Posting updates or alerts from an MCP server to a community.
  3. Integrating server events with Discord for real-time communication.

FAQ from MCP Server Discord Webhook?

  • How do I install the MCP Server Discord Webhook?

You can install it using the command: npm install @genpm/mcp-server-discord-webhook.

  • What do I need to configure?

You need to add your Discord webhook URL in the MCP configuration file.

  • Can I customize the message sender's name?

Yes! You can specify a custom username and avatar URL when sending messages.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
0
Language
JavaScript
License
MIT license

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

37 minutes ago