Evento Public MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PUBLIC_API_KEY | No | Developer-facing Evento API key used as Authorization: Bearer <key> | |
| EVENTO_API_BASE_URL | No | Base URL of the Evento API | https://evento.so/api |
| EVENTO_API_TIMEOUT_MS | No | Timeout in milliseconds for API calls | 15000 |
| EVENTO_PUBLIC_API_KEY | No | Legacy compatibility fallback if PUBLIC_API_KEY is missing | |
| EVENTO_SMOKE_USERNAME | No | Username used by smoke command (optional) | |
| EVENTO_API_RETRY_ATTEMPTS | No | Number of retry attempts on failure | 2 |
| EVENTO_API_RETRY_DELAY_MS | No | Delay in milliseconds between retries | 250 |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list-eventsB | List events for a specific user. Returns upcoming, past, or all profile events. |
| get-eventA | Get detailed information about a specific event by its ID. |
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 2 tools
list-events returns a collection of events for a user, while get-event returns details for a single event by ID. The purposes are clearly distinct and unlikely to be confused.
Both tools follow the same kebab-case verb-noun pattern: list-events and get-event. The naming is consistent and predictable.
Two tools is minimal for a server, though acceptable for a narrow read-only event API. It falls below the typical well-scoped 3-15 tool range.
The core read workflow is covered: listing events and fetching event details. There are minor gaps such as no search or filter-by-date tool, but for a public read-only event server this is reasonable.