Skip to main content
Glama
kevinnz

pretalx-mcp

by kevinnz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to pretalx-mcp

No user-submitted related servers found.

    Related Servers

    • call-copilot

      AnisurRahmann
      A
      license
      Not graded
      quality
      A
      maintenance
      Search and read locally-recorded meeting transcripts over stdio. Read-only, no network. Exposes list_sessions, get_session, and search_transcripts to any MCP client.
      46 PyPI
      7
      MIT

    • engineering-bridge

      wudy29
      A
      license
      Not graded
      quality
      A
      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.
      130
      MIT

    • Superset MCP Server

      Amit-DAlal-1
      F
      license
      B
      quality
      C
      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
      -

    • mcp-model-proxy

      jfdjaf
      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
      8
      MIT

    • @guedder/mcp

      guedder
      F
      license
      Not graded
      quality
      B
      maintenance
      Readonly MCP server for the Guedder API v3, enabling operational tasks like listing events, searching tickets, and managing purchases via Streamable HTTP or stdio.
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    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
    ResponsivenessNo issues

    Resources