EventHorizon MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Log level: debug, info, warn, error | info |
| API_TIMEOUT | No | Request timeout in milliseconds | 30000 |
| EVENTHORIZON_BASE_URL | No | EventHorizon API URL | http://localhost:8000 |
| EVENTHORIZON_API_TOKEN | Yes | Knox authentication token |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_eventsC | List all available events. Optionally filter by search term or location. |
| get_eventC | Get detailed information about a specific event by its ID. |
| create_eventC | Create a new event. Requires title, description, start/end times, location, and capacity. |
| update_eventB | Update an existing event. Only provide the fields you want to change. |
| delete_eventA | Delete an event. Only the organizer can delete their events. |
| register_for_eventC | Register the current user for an event. |
| unregister_from_eventC | Unregister the current user from an event. |
| get_event_registrationsB | Get all registrations for an event. Only available to the event organizer. |
| manage_registrationA | Manage a registration (approve, waitlist, or cancel). Only available to the event organizer. |
| get_my_profileB | Get the current user's profile information. |
| get_my_registrationsB | Get all events the current user is registered for. |
| get_my_hosted_eventsB | Get all events organized by the current user. |
| health_checkA | Check the connection to the EventHorizon API and verify authentication. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 13 tools
Every tool has a clearly distinct purpose with no overlap. For example, get_event retrieves event details while get_event_registrations focuses on attendee data, and tools like register_for_event and unregister_from_event are precise opposites. The descriptions reinforce these distinctions, making misselection unlikely.
All tools follow a consistent verb_noun pattern using snake_case, such as create_event, list_events, and get_my_profile. The naming is predictable and readable throughout, with no deviations in style or convention, which aids agent comprehension.
With 13 tools, the count is well-scoped for an event management domain, covering core operations like CRUD for events, registration handling, and user-specific queries. Each tool earns its place without redundancy, fitting typical server scope expectations.
The toolset provides complete coverage for event management, including full CRUD for events (create, get, update, delete), registration lifecycle (register, unregister, manage), and user-specific views (hosted events, registrations, profile). There are no obvious gaps, ensuring agents can handle end-to-end workflows without dead ends.