Mirobody
Lab results to LOINC codes and UCUM units, symptoms and diagnoses to ICPC-3. Offline, no API key.
作者提供的说明(英文原文)
Ask your AI about your product's events, delivery health and usage
这三项永远不会合并成一个分数:意见、测量和人气是不同的东西。
我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。
选择你使用的 AI 应用,然后复制设置。
你需要
你用的是哪个应用?
在上方选择你的应用。我们会记住它,下次按钮会显示“安装到 …”。
适用于网页版、桌面版和手机版 Claude:
https://eventsend.io/mcp在终端中运行这条命令
claude mcp add --transport http eventsend https://eventsend.io/mcp粘贴到项目中的 .cursor/mcp.json,或 ~/.cursor/mcp.json
{
"mcpServers": {
"eventsend": {
"url": "https://eventsend.io/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
粘贴到项目中的 .vscode/mcp.json
{
"servers": {
"eventsend": {
"type": "http",
"url": "https://eventsend.io/mcp"
}
}
}浏览器会先询问是否打开应用,然后应用会显示设置并请你确认。密钥的值会留空,由你自己填写。
ChatGPT 只能连接互联网上的服务器:
https://eventsend.io/mcp菜单名称可能因套餐和版本不同而略有差异。
你的选择通过 Cookie 保存在这台设备上,无需账户。
这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。
我们还没有读取这个服务器的工具列表;我们会轮流检查各个端点。
我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月6日
注册名称已通过域名 eventsend.io 验证(注册中心会核实域名所有权)
我们还没有从 GitHub 读取这个仓库
我们还没有从 GitHub 读取这个仓库
尚未检查;我们会轮流检查各个端点
尚未检查;我们会轮流检查各个端点
尚未检查;我们会在检查端点时读取工具列表
与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。
它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。
注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。
它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。
GitHub 仓库最后更新于–,最新版本(1.0.1)于9天前进入注册中心。
支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,所以接受远程 MCP 服务器的应用也可以使用,例如开启开发者模式的 ChatGPT。
同一分类中有:Mirobody, FHIR MCP Server, Google Health MCP
同一分类中其他作者的服务器,按星标数排序。
如何看卡片:★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i
Lab results to LOINC codes and UCUM units, symptoms and diagnoses to ICPC-3. Offline, no API key.
MCP server providing seamless access to FHIR APIs for AI tools and healthcare applications
Privacy-first unofficial Google Health API v4 MCP server for health, sleep, activity, HR agents
按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。
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.
cus_9Xk2 do before they cancelled?"deploy.failed events go?"| Skill | What it does |
|---|---|
investigate-failures | Finds 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-timeline | Rebuilds one customer's history from every event that carries their user_id, oldest first, with the moments that matter called out. |
activity-report | Summarizes a day, a week or a month: volume against the previous period, top events, errors, delivery problems and quota. |
routing-map | Explains 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.
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:
claude plugin marketplace add mytinyrocket/eventsend-claude-plugin
claude 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.
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.
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.
Open an issue in this repository, or email support@eventsend.io.
MIT