Webhook Admin

com.webhookadminPublished by webhookadmin.comOfficial publisherv1.0.2Updated Oct 28, 2026

Webhook の送信・再送・監視を行う Webhook 統合インテグレーション (日本製)。送信先・イベントの種類・API キーを tool で扱う。管理画面のアカウントでログイン (OAuth)

VerifiedStreamable HTTPWeb executableProductivity & WorkflowDeveloper Tools

Overview

AI-generated overview

Webhook Admin is a remote MCP server for sending, resending and monitoring webhooks, with destinations, event types and API keys handled through tools.

What you can do
  • Send webhooks to configured destinations
  • Resend previously sent webhooks
  • Monitor webhook delivery
  • Manage destinations, event types and API keys through tools
When to use it
Useful when an assistant should trigger or retry outbound webhook deliveries and check their status, for example to wire events from other systems into webhook endpoints without leaving the chat.
Requirements
A remote MCP endpoint at api.webhookadmin.com over streamable HTTP. OAuth login with a Webhook Admin management-console account is required. No environment variables or headers are declared.
Before you install
The tools handle API keys and webhook destinations, so the assistant may be able to read or change credentials and endpoints. Sending and resending webhooks pushes data to third-party destinations and can trigger actions on the receiving side; review what is sent before enabling.

Installation

In SourceWeft

  1. Open Webhook Admin in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.webhookadmin%2Fwebhookadmin/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "webhook-admin": {
      "type": "http",
      "url": "https://api.webhookadmin.com/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

3
  1. v1.0.2LatestOct 20, 2026
  2. v1.0.1Sep 27, 2026
  3. v1.0.0Sep 27, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.