Content
# eventing-mcp
TypeScript MCP server for the Eventing project, built with the official Model Context Protocol SDK.
## Scripts
- `npm run dev` starts the Streamable HTTP server from TypeScript.
- `npm run build` compiles TypeScript into `dist`.
- `npm start` runs the compiled Streamable HTTP server.
## Server
The server exposes Streamable HTTP only. It does not support stdio.
- MCP endpoint: `http://127.0.0.1:7988/mcp`
- Health endpoint: `http://127.0.0.1:7988/health`
- Environment variables are loaded from `.env` automatically. Use `.env.example` as the template.
- `PORT` sets the listen port. Defaults to `7988`.
- `HOST` sets the bind host. Defaults to `127.0.0.1`.
- `API_ENDPOINT` sets the Eventing backend API endpoint. Defaults to `https://ievent.life/API`.
## Tools
All backend tools are read-only GET requests. They unwrap the backend response and return the API response `data` field as JSON text. Object-shaped data is also exposed as `structuredContent`; array-shaped data is exposed as `structuredContent.items` because MCP structured content must be an object.
- `search_events`: calls `GET /Event/searchV2` and returns `EventPagination`.
- Inputs: `keyword?`, `areaCode?`, `date?`, `startDate?`, `endDate?`, `tags?`, `page?`, `sort?`.
- `get_event_detail`: calls `GET /Event/find` and returns `EventDetailResponse`.
- Inputs: `id`.
- `search_persons`: calls `GET /Person/searchV2` and returns `PersonRecord[]`.
- Inputs: `keyword`.
- `get_person_detail`: calls `GET /Person/find` and returns `PersonDetailResponse`.
- Inputs: `id`.
- `get_person_recent_events`: calls `GET /Event/personRecent` and returns recent event basic info only.
- Inputs: `pid`, `page?`.
- `search_locations`: calls `GET /Location/searchV2` and returns `LocationRecord[]`.
- Inputs: `keyword`.
- `get_location_detail`: calls `GET /Location/find` and returns `LocationDetailResponse`.
- Inputs: `id`.
- `get_location_recent_events`: calls `GET /Event/locationRecent` and returns recent event basic info only.
- Inputs: `locationId`, `page?`.
## MCP Client Config
Point Streamable HTTP-capable MCP clients at the remote endpoint:
```json
{
"mcpServers": {
"eventing-mcp": {
"url": "http://127.0.0.1:7988/mcp"
}
}
}
```
Connection Info
You Might Also Like
Train-in-Silence
The first Task-Aware MCP server and automated VRAM calculator for LLM...
stacklit
108,000 lines of code. 4,000 tokens of index. One command makes any repo...
AppClaw
AI-powered mobile automation agent — describe what you want in plain...
pdf-mcp
Production-ready MCP server for PDF processing with intelligent caching....
kotadb
Local-only code intelligence API for AI developer workflows (Bun +...
gemini-api-docs-mcp
A remote HTTP MCP server for searching Google Gemini API documentation.