Skip to main content
Glama

pretalx-mcp (local-only)

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 API

Only outbound HTTPS requests to pretalx are expected. No inbound network service is exposed.

Features

  • 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

Installation

  1. Install Python 3.11+ and uv.

  2. Clone this repository.

  3. Sync dependencies:

uv sync

Configuration

Copy .env.example to .env and fill in local values:

cp .env.example .env

Variable

Required

Default

Notes

PRETALX_BASE_URL

Yes

none

pretalx base URL, no trailing slash

PRETALX_API_TOKEN

Yes

empty

use a local token; never commit

PRETALX_DEFAULT_EVENT

No

empty

optional fallback event slug

PRETALX_TIMEOUT_SECONDS

No

20

HTTP timeout in seconds

PRETALX_VERIFY_TLS

No

true

keep TLS verification enabled

PRETALX_READ_ONLY

No

true

must remain true for v1

PRETALX_TRANSPORT

No

stdio

only supported value is stdio

Running locally

Run the server locally with stdio transport:

uv run pretalx-mcp

This process is intended to be launched by an MCP client, not exposed as a web service.

MCP client configuration

See docs/MCP_CLIENT_SETUP.md for a generic MCP client JSON configuration using:

uv --directory /path/to/pretalx-mcp run pretalx-mcp

Security notes

  • Keep 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.

Development

Common local commands:

uv sync
uv run ruff check .
uv run pytest

Project docs and metadata files:

  • .env.example

  • .gitignore

  • docs/SECURITY.md

  • docs/MCP_CLIENT_SETUP.md

Roadmap

  • 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.

Available Tools

14 tools
pretalx_find_schedule_conflictsC

Detect potential overlaps and missing schedule data.

Inputs: event. Returns: object

pretalx_get_eventC

Fetch one event in detail.

Inputs: event, include_raw. Returns: object

pretalx_get_scheduleB

Fetch and summarise the current schedule for an event.

Inputs: event, include_raw. Returns: object

pretalx_get_speakerB

Fetch one speaker profile with submission context.

Inputs: event, speaker, include_raw. Returns: object

pretalx_get_submissionB

Fetch full details for one submission.

Inputs: event, include_raw, submission_code. Returns: object

pretalx_get_submission_reviewsA

Get reviews for one submission and degrade gracefully when unavailable.

Inputs: event, include_raw, submission_code. Returns: object

pretalx_list_eventsC

List visible events in a compact form.

Inputs: limit, include_raw. Returns: object

pretalx_list_schedule_sessionsC

Flatten schedule sessions with optional case-insensitive filters.

Inputs: day, room, event, track, +2 more. Returns: object

pretalx_list_speakersC

List speakers for an event with compact output.

Inputs: event, limit, include_raw. Returns: object

pretalx_list_submissionsC

List submissions for an event with optional server-side filters.

Inputs: event, limit, state, track, +2 more. Returns: object

pretalx_review_summaryB

Summarise review coverage and score trends for an event.

Inputs: event. Returns: object

pretalx_search_speakersA

Search speakers by name/email server-side and bio/submission titles locally.

Inputs: event, limit, query, include_raw. Returns: object

pretalx_search_submissionsC

Search submissions using server-side q plus local matching.

Inputs: event, limit, query, state, +3 more. Returns: object

pretalx_summarise_submissionsC

Summarise submissions grouped by one selected attribute.

Inputs: event, group_by. Returns: object

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    B3.3/5.0

    Scored across 14 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness5/5

    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.

    Maintenance

    ActivityInactive
    ResponsivenessOutdated data

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      B
      quality
      D
      maintenance
      A minimal local MCP server that wraps any Claude Messages API-compatible upstream into a unified ask_model tool. It enables MCP clients to interact with these models through a standard tool interface using stdio transport.
      1
      7
      MIT
    • F
      license
      B
      quality
      D
      maintenance
      Local stdio MCP server for reviewing Apache Superset dashboards, retrieving chart data, executing SQL through SQL Lab, and creating or updating saved queries.
      25
      1
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      A local STDIO MCP server that bridges MCP clients to the Codex CLI by sending instructions to a configured workspace, exposing task run, status, and result tools with a read-only sandbox and no remote transport.
      137
      MIT