
Eventsorg Mcp
io.github.guth01由 GitHub 帳號 guth01 發布v1.0.2更新於 Oct 26, 2026
Autonomous MCP server and background agent for managing live event logistics.
概覽
本機 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 網址等選用設定。一次部署只服務一場活動。
安裝
在 SourceWeft 中
- 開啟 儀表板中的 Eventsorg Mcp,將其新增到工作區。
- 為需要使用其工具的對話啟用該服務。
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 yourlocalhostduring 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:
- Twilio (Account SID, Auth Token, Phone Number)
- Google Cloud (Service Account JSON with Sheets API enabled)
- Google Gemini (For the autonomous agent)
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:
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.
- Open your
claude_desktop_config.jsonfile. - Add this configuration (inserting your own API keys):
- 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:
- Rent a cloud server and run the package in HTTP mode:
- The server spins up and listens at your URL (e.g.,
https://your-server.com/sse). - Now, in your custom app, you can connect remotely using the official MCP SDK:
(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):
- Clone the repository and run
npm install. - Copy
.env.exampleto.envand fill in your keys. - Run
npm run start(for the API) ornpm 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):
- Push this code to your own GitHub repo.
- Connect your repository to your cloud provider and deploy it.
- Paste your
.envvariables into your cloud provider's dashboard. - Ensure your provider gives you a public URL (e.g.,
https://my-events.onrender.com), and set this as thePUBLIC_URLenvironment variable. - 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版本歷史
1- v1.0.2最新Sep 16, 2026
評分
已滿足適用檢查項的 50%
該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。
- 近 30 天內可連通25 分
請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。
- 已宣告認證方式10 分
請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。
- 已列出工具15 分
請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。
- 描述必需15 分
- 圖示10 分
- 文件15 分
- 授權條款10 分