Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@pretalx-mcp get the schedule for the next event"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
pretalx-mcp is a local MCP server for pretalx. It is designed to run as a
child process of a local MCP client and communicates over stdio only.
Local MCP client -> local stdio MCP process -> outbound HTTPS -> pretalx APIOnly outbound HTTPS requests to pretalx are expected. No inbound network service is exposed.
Local-only architecture (no hosted or remote MCP endpoint).
stdio is the only supported transport.
Read-only by default (PRETALX_READ_ONLY=true).
Environment-based configuration via .env.
MCP tools for events, submissions, speakers, schedule, and optional reviews.
Related MCP server: Superset MCP Server
Install Python 3.11+ and uv.
Clone this repository.
Sync dependencies:
uv syncCopy .env.example to .env and fill in local values:
cp .env.example .envVariable | Required | Default | Notes |
| Yes | none | pretalx base URL, no trailing slash |
| Yes | empty | use a local token; never commit |
| No | empty | optional fallback event slug |
| No |
| HTTP timeout in seconds |
| No |
| keep TLS verification enabled |
| No |
| must remain true for v1 |
| No |
| only supported value is |
Run the server locally with stdio transport:
uv run pretalx-mcpThis process is intended to be launched by an MCP client, not exposed as a web service.
See docs/MCP_CLIENT_SETUP.md for a generic MCP client JSON configuration using:
uv --directory /path/to/pretalx-mcp run pretalx-mcpKeep API tokens local and out of git history.
Prefer least-privilege, read-only pretalx tokens.
Never log or print tokens.
Do not run this project as a hosted/cloud MCP service.
See docs/SECURITY.md for full guidance.
Common local commands:
uv sync
uv run ruff check .
uv run pytestProject docs and metadata files:
.env.example
.gitignore
docs/SECURITY.md
docs/MCP_CLIENT_SETUP.md
Deliver read-only organiser workflows first.
Keep transport local (stdio) and avoid any remote server mode.
Add optional review-oriented tools where API permissions allow.
Consider future write tools only behind explicit safety checks and opt-in configuration.
Detect potential overlaps and missing schedule data.
Inputs: event. Returns: object
Fetch one event in detail.
Inputs: event, include_raw. Returns: object
Fetch and summarise the current schedule for an event.
Inputs: event, include_raw. Returns: object
Fetch one speaker profile with submission context.
Inputs: event, speaker, include_raw. Returns: object
Fetch full details for one submission.
Inputs: event, include_raw, submission_code. Returns: object
Get reviews for one submission and degrade gracefully when unavailable.
Inputs: event, include_raw, submission_code. Returns: object
List visible events in a compact form.
Inputs: limit, include_raw. Returns: object
Flatten schedule sessions with optional case-insensitive filters.
Inputs: day, room, event, track, +2 more. Returns: object
List speakers for an event with compact output.
Inputs: event, limit, include_raw. Returns: object
List submissions for an event with optional server-side filters.
Inputs: event, limit, state, track, +2 more. Returns: object
Summarise review coverage and score trends for an event.
Inputs: event. Returns: object
Search speakers by name/email server-side and bio/submission titles locally.
Inputs: event, limit, query, include_raw. Returns: object
Search submissions using server-side q plus local matching.
Inputs: event, limit, query, state, +3 more. Returns: object
Summarise submissions grouped by one selected attribute.
Inputs: event, group_by. Returns: object
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
The official Planning Center MCP server for interacting with your ministry's data.
The official MCP Server for the Mux API
Ovanek MCP: Model Context Protocol server for Ovanek platform tools; writes are dry-run by default.
Historical tick, order book and settlement data for Polymarket and Predict.fun crypto up/down markets, plus smart-money lists and backtest quotes, over a read-only MCP server.
