pretalx-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PRETALX_BASE_URL | Yes | pretalx base URL, no trailing slash | |
| PRETALX_API_TOKEN | Yes | use a local token; never commit | |
| PRETALX_READ_ONLY | No | must remain true for v1 | true |
| PRETALX_TRANSPORT | No | only supported value is stdio | stdio |
| PRETALX_VERIFY_TLS | No | keep TLS verification enabled | true |
| PRETALX_DEFAULT_EVENT | No | optional fallback event slug | |
| PRETALX_TIMEOUT_SECONDS | No | HTTP timeout in seconds | 20 |
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 | {
"listChanged": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| pretalx_list_eventsC | List visible events in a compact form. |
| pretalx_get_eventC | Fetch one event in detail. |
| pretalx_list_submissionsC | List submissions for an event with optional server-side filters. |
| pretalx_get_submissionB | Fetch full details for one submission. |
| pretalx_search_submissionsC | Search submissions using server-side q plus local matching. |
| pretalx_summarise_submissionsC | Summarise submissions grouped by one selected attribute. |
| pretalx_list_speakersC | List speakers for an event with compact output. |
| pretalx_get_speakerB | Fetch one speaker profile with submission context. |
| pretalx_search_speakersA | Search speakers by name/email server-side and bio/submission titles locally. |
| pretalx_get_scheduleB | Fetch and summarise the current schedule for an event. |
| pretalx_list_schedule_sessionsC | Flatten schedule sessions with optional case-insensitive filters. |
| pretalx_find_schedule_conflictsC | Detect potential overlaps and missing schedule data. |
| pretalx_get_submission_reviewsA | Get reviews for one submission and degrade gracefully when unavailable. |
| pretalx_review_summaryB | Summarise review coverage and score trends for an event. |
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 14 tools
Each tool targets a distinct resource and action: events, speakers, submissions, schedule, and reviews are clearly separated. Search and list variants are differentiated by search intent versus full listing, and summary tools are distinct from detailed get tools.
All tools follow a consistent verb_noun pattern with the pretalx_ prefix, using lowercase snake_case throughout. The naming convention is uniform, making the tool set predictable and easy to navigate.
With 14 tools, the server is well-scoped for a conference management domain. Each tool covers a necessary operation without redundancy, fitting the typical 3-15 tool range comfortably.
The tool surface comprehensively covers the read-only needs of a Pretalx event management system: events, speakers, submissions, schedule, and reviews are all addressed. It includes listing, getting, searching, and summarizing operations, with no obvious gaps in core workflows.