Eventsorg Mcp

io.github.guth01由 GitHub 账号 guth01 发布v1.0.2更新于 Oct 26, 2026

Autonomous MCP server and background agent for managing live event logistics.

概览

AI 生成的概览

本地 MCP 服务器,让助手管理现场活动后勤:读取活动数据、调配志愿者、取消供应商,并向工作人员发送短信。

可以做什么
  • 读取活动概况、事件记录、供应商签到状态及数据库中的具体数据
  • 调配志愿者、取消供应商时段、将区域移至室内,并升级上报给协调员
  • 向工作人员发送短信并查看短信记录,收到的回复会自动写回数据库
  • 将当前数据库状态同步到 Google 表格看板
  • 查询路线与天气,用于调配人员或预警降雨风险
适用场景
适合希望由 AI 助手协助统筹单场现场活动的组织者,例如处理供应商迟到、区域人手不足或天气问题,并给相关人员发短信。也可用于在作者提供的公开示例活动实例上试用活动管理工具。
运行要求
通过 npx 以本地 Node.js 进程运行(npm 包 eventsorg-mcp),通常配置在 Claude Desktop 或 Cursor 中,电脑需保持开机运行。需要 GOOGLE_API_KEY、TWILIO_ACCOUNT_SID、TWILIO_AUTH_TOKEN 和 TWILIO_PHONE_NUMBER。README 还列出天气、地图、SMTP 邮件、Google 表格及公开 webhook 地址等可选配置。一次部署只服务一场活动。
安装前请注意
保存 Twilio 与 Google 凭据,可发送真实且计费的短信并写入 Google 表格。相关工具会修改数据:调配志愿者、取消供应商时段、移动区域和升级上报。README 提醒启动脚本会写入虚假示例数据,真实活动前必须移除。可选的 HTTP/SSE 模式会把服务器公开到网络,公开测试实例每次启动都会清空数据库。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Eventsorg Mcp,将其添加到工作区。
  2. 为需要使用其工具的对话启用该服务。

Desktop only,通过 STDIO。 STDIO 服务会启动本地进程,因此需要 SourceWeft 桌面宿主。

其他 MCP 客户端

参照 仓库 中的启动说明。

README

🌐 EventsOrg MCP: Autonomous AI Event Manager

[MCP Registry] [NPM Version] [MCP Server] [AI Agent] [TypeScript] [License]

An open-source Model Context Protocol (MCP) server and background autonomous agent designed to run the logistics of live events.

EventsOrg MCP gives LLMs (like Claude and Gemini) the "hands" to read live event data, reassign volunteers, cancel missing vendors, and communicate with staff via physical SMS messages.

Note: This repository is a framework. It is designed so that any event organizer can deploy their own instance of this code, attach their own API keys, and manage their own isolated event.


✨ Features

  • MCP Protocol Native: Exposes over 20+ event management tools (e.g., reassign_volunteer, get_vendor_status) to any standard AI client.
  • Twilio SMS Orchestration: The AI can text volunteers physical SMS messages. Inbound SMS replies are automatically parsed and routed back into the database.
  • Autonomous Agent Loop: Includes a standalone Gemini-powered agent (agent.ts) that runs 24/7, actively monitoring the event and resolving issues before a human even notices.
  • Google Sheets Sync: Automatically pushes real-time database state to a Google Sheets dashboard for human coordinators to view.
  • Zero-Config Local Webhooks: Uses Cloudflare Tunnels (untun) to automatically route live Twilio SMS back to your localhost during development.

🏗 Architecture & Use Cases

This codebase supports three entirely different ways to interact with the AI:

1. Local Desktop Plugin (stdio)

Perfect for solo event organizers or local development. By connecting the code to Claude Desktop or Cursor, the AI talks directly to the local SQLite database via standard terminal input/output (stdio).

  • Requires: Your laptop to stay open and running.

2. Public API for AI (HTTP / SSE)

By starting the server with the --transport http flag, you turn the local server into a globally accessible web API. Other developers, LangChain apps, or AI IDEs can connect to your event remotely using Server-Sent Events (SSE).

  • Requires: Deployment to a cloud host like Railway, AWS, or Render.

3. The Autonomous Virtual Coordinator

You don't even need a chat window. By running the included agent.ts script, a Gemini-powered worker wakes up every 5 minutes, checks the database for anomalies (missing vendors, safety incidents, weather alerts), fixes them, and texts the staff—completely autonomously.

4. Packaged Agent Skill (SKILL.md)

EventsOrg is packaged as a standard Agent Skill compliant with the open SKILL.md specification and listed on marketplaces like Agensi.io. It provides AI agents (Claude Code, Cursor, Copilot) with explicit SOPs, incident triage rules, and real-time SMS dispatch protocols out of the box.

  • Package folder: skills/event-logistics-coordinator/

🚀 How to Deploy Your Own Event

Because this system uses a local SQLite database (grid.db), one deployment equals one event. If multiple organizers want to run different events, they must deploy their own separate instances of this code.

Prerequisites

You will need API keys for:

Environment Variables

Copy the .env.example file to .env and configure your API keys before starting the server. Alternatively, if deploying to a cloud platform (like Render, AWS, or Railway), add these directly to your dashboard:

env
# AI ModelsGOOGLE_API_KEY=your_gemini_api_key
# Twilio SMS EngineTWILIO_ACCOUNT_SID=your_twilio_sidTWILIO_AUTH_TOKEN=your_twilio_tokenTWILIO_PHONE_NUMBER=+1234567890
# External IntegrationsOPENWEATHER_API_KEY=your_openweather_keyGOOGLE_MAPS_API_KEY=your_maps_key
# Escalation Emails[email protected][email protected]SMTP_PASS=your_app_password
# Webhook ConfigPUBLIC_URL=eventsorg-mcp-production.up.railway.app # Set this when deployed publiclyWEBHOOK_PORT=3000
# Google Sheets SyncGOOGLE_SHEET_ID=your_google_sheet_idGOOGLE_SERVICE_ACCOUNT_JSON='{ "type": "service_account", ... }'

1. Using with Claude Desktop (stdio mode)

The easiest way to use this is as a local plugin for Claude. Since it's published to NPM, you don't even need to clone the repo.

  1. Open your claude_desktop_config.json file.
  2. Add this configuration (inserting your own API keys):
    json
    {  "mcpServers": {    "eventsorg-mcp": {      "command": "npx",      "args": ["-y", "eventsorg-mcp"],      "env": {        "TWILIO_ACCOUNT_SID": "your_twilio_sid",        "TWILIO_AUTH_TOKEN": "your_twilio_token",        "TWILIO_PHONE_NUMBER": "+1234567890",        "GOOGLE_API_KEY": "your_gemini_api_key"      }    }  }}
  3. Restart Claude Desktop.

Example usage: Open Claude and say, "My security vendor just called and said they are 30 minutes late. Can you update the system and text the outdoor zone volunteers?" Claude will instantly talk to your NPM package in the background, update the local database, and send the Twilio texts.

2. Standalone Cloud API (SSE mode)

If you want to build a custom web app or allow remote agents (like LangChain or custom scripts) to manage your event over the internet:

  1. Rent a cloud server and run the package in HTTP mode:
    bash
    npx -y eventsorg-mcp --transport http
  2. The server spins up and listens at your URL (e.g., https://your-server.com/sse).
  3. Now, in your custom app, you can connect remotely using the official MCP SDK:
    javascript
    import { Client } from "@modelcontextprotocol/sdk/client/index.js";import { SSEClientTransport } from "@modelcontextprotocol/sdk/client/sse.js";
    const transport = new SSEClientTransport("https://your-server.com/sse");const mcpClient = new Client();await mcpClient.connect(transport);
    // Trigger tools remotely over the internet!await mcpClient.callTool({ name: "get_event_summary", arguments: {} });

(Note: Ensure you have your environment variables set in your terminal or cloud dashboard before running the npx command).

3. Developer Setup (Cloning)

If you want to modify the code or run the autonomous background agent (agent.ts):

  1. Clone the repository and run npm install.
  2. Copy .env.example to .env and fill in your keys.
  3. Run npm run start (for the API) or npm run start:agent (for the autonomous worker).

Cloud Deployment

If you want to host this publicly so an AI can manage it 24/7 in the cloud, you can deploy this on any Node.js hosting provider (like Render, AWS, Railway, Heroku, or Fly.io):

  1. Push this code to your own GitHub repo.
  2. Connect your repository to your cloud provider and deploy it.
  3. Paste your .env variables into your cloud provider's dashboard.
  4. Ensure your provider gives you a public URL (e.g., https://my-events.onrender.com), and set this as the PUBLIC_URL environment variable.
  5. In your Twilio console, point your phone number's webhook to https://<YOUR-PUBLIC-URL>/webhook/sms.

(Note: The npm start command will automatically seed the database with fake "sample event" data. If you are running a real event, remove tsx src/seed.ts from the start script in package.json!)


🧪 Testing with the Live "Sample Event"

If you just want to test how the MCP protocol works without hosting a real event, I have deployed a public test instance of this server. Every time this test server boots, it completely wipes the database and fills it with a chaotic, half-broken music festival (vendors are 45 minutes late, zones are short-staffed).

You can build or connect your own MCP clients (like LangChain, custom apps, or AI code editors) to test it right now!

Live Test SSE Endpoint: https://eventsorg-mcp-production.up.railway.app/sse

Connect your AI to this URL and ask it: "What is the status of my event?" Watch as it identifies the issues and fires off physical text messages to try and save the festival!


🛠 Available MCP Tools

This MCP server exposes over 20+ tools to give your AI full operational control over the event. Here are the main highlights:

  • 📱 Twilio SMS Orchestration: (send_sms, get_sms_history) Allows the AI to text staff directly. Inbound replies are automatically logged to the database via webhook.
  • 📊 Google Sheets Dashboard: (sync_to_sheets) Pushes the real-time state of the database to a remote Google Sheet for human coordinators.
  • 🗺️ Maps & Weather: (get_directions, get_weather) Provides the AI with live contextual data, such as walking times for reassigning volunteers or rain alerts for outdoor zones.
  • 🔍 Core Operations: (get_event_summary, reassign_volunteer, cancel_vendor_slot, escalate_to_coordinator, move_zone_indoors)

(Note: This is just a highlight! The server includes many more granular tools for managing incidents, checking in vendors, and querying exact database state.)


📄 License

This project is licensed under the ISC License.

来源:README.md,提交 5b8a48b

工具

0
SourceWeft 尚未在沙箱中启动过该软件包,因此其工具未知。

版本历史

1
  1. v1.0.2最新Sep 16, 2026

评分

已满足适用检查项的 50%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通25 分

    请保持端点能够响应 MCP 握手;SourceWeft 每 30 天探测一次。

  • 已声明认证方式10 分

    请在注册中心条目中声明凭据请求头,或保持端点能够响应探测,以便判定其认证方式。

  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分