EventSend

io.eventsendPublished by eventsend.ioOfficial publisherv1.0.1Updated Oct 29, 2026

Ask your AI about your product's events, delivery health and usage

VerifiedStreamable HTTPWeb executableCommunication & CollaborationSecurity & MonitoringData & Analytics

Overview

AI-generated overview

Read-only remote MCP server that lets an assistant answer questions about your EventSend product events, notification delivery health and usage.

What you can do
  • Investigate failed or missing notifications: delivery health per destination, event status, exact errors and what to fix
  • Rebuild a single customer's timeline from every event carrying their user_id, oldest first
  • Summarize a day, week or month: volume versus the previous period, top events, errors, delivery problems and quota
  • Explain routes, sources, topics and destinations, and trace where a given event is delivered and why
  • Search events and read payloads, delivery records, daily counts and quota for the organizations you approved
When to use it
Useful when you route product events through EventSend to Slack, Discord, Telegram, webhooks or push and want to ask in plain language what happened, why an alert did not arrive, or how usage compares with the previous period.
Requirements
A remote MCP endpoint at eventsend.io, reachable over streamable HTTP. An EventSend account on any plan, including Free. OAuth sign-in, during which you choose which organizations the connection may read. No environment variables or headers are declared.
Before you install
Sign-in uses OAuth and the connection sees what you can see in the organizations you approve, so grant only the organizations you intend. Tool arguments such as search text, event names, customer identifiers, organization names and dates are sent to EventSend, and returned event payloads, delivery records and errors become part of the conversation. The server is described as read-only and unable to create, change or delete anything; revoke access under Connected apps or via an organization…

Installation

In SourceWeft

  1. Open EventSend 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/io.eventsend%2Feventsend/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": {
    "eventsend": {
      "type": "http",
      "url": "https://eventsend.io/mcp"
    }
  }
}

README

EventSend for Claude

EventSend routes your product's events, like payments, signups, deploys and errors, to Slack, Discord, Telegram, webhooks and push notifications. This plugin lets Claude answer questions about those events in plain language: what happened, to whom, and whether the notifications got through.

It connects Claude to EventSend's read-only MCP server and adds four skills that teach Claude how to investigate with it. Nothing it does can change your EventSend account.

What you can ask

  • "Did anything fail in checkout today?"
  • "Why didn't the payment alert reach #billing this morning?"
  • "What did customer cus_9Xk2 do before they cancelled?"
  • "Give me a summary of last week compared with the week before."
  • "Where do deploy.failed events go?"
  • "Are we going to run out of events before the month ends?"

Skills

SkillWhat it does
investigate-failuresFinds out why a notification failed or never arrived: delivery health per destination, the event's status, the exact errors, and what to fix in EventSend.
customer-timelineRebuilds one customer's history from every event that carries their user_id, oldest first, with the moments that matter called out.
activity-reportSummarizes a day, a week or a month: volume against the previous period, top events, errors, delivery problems and quota.
routing-mapExplains your routes, sources, topics and destinations, and traces where a given event is delivered and why.

Claude picks the right skill from your question. In Claude Code you can also run one directly, for example /eventsend:activity-report.

Install

You need an EventSend account. Every plan works, including Free.

claude.ai and Cowork: add EventSend from the plugin directory in Customize → Plugins. Then open the plugin's Connectors tab, connect EventSend, sign in, and choose which of your organizations Claude may read.

Claude Code:

bash
claude plugin marketplace add mytinyrocket/eventsend-claude-pluginclaude plugin install eventsend@eventsend

Then run /mcp, select eventsend and sign in. Your browser opens EventSend, where you choose the organizations to connect.

Gemini CLI: this repository is also a Gemini CLI extension.

bash
gemini extensions install https://github.com/mytinyrocket/eventsend-claude-plugin

Then run /mcp auth eventsend and sign in.

Cursor, ChatGPT and other clients: the same server works in any client that supports remote MCP servers. See the client setup guide for each one.

Data and privacy

The plugin runs no code of its own and stores nothing. It contains instructions for Claude and one connector reference, to https://eventsend.io/mcp.

When Claude uses an EventSend tool, the tool's arguments go to EventSend: search text, event names, customer identifiers, organization names and dates. What comes back is your organization's data, which then becomes part of your conversation with Claude. That covers events and their payloads, delivery records and errors, daily counts, quota, and the names and ids of your routes, sources, topics and destinations. No tool returns ingest tokens, signing secrets, MCP keys or destination settings, and no tool can create, change or delete anything.

Sign-in uses OAuth. A connection sees exactly what you can see in the organizations you approved. To revoke it, disconnect under Connected apps in your EventSend settings, or ask an organization owner or admin to remove it under Settings → MCP. Revocation takes effect on the next request.

Support

Open an issue in this repository, or email [email protected].

License

MIT

Source: README.md at commit 9b30aba

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

2
  1. v1.0.1LatestOct 29, 2026
  2. v1.0.0Sep 19, 2026

Score

85% 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
  • License10 pts