EventDorm

com.eventdormPublished by eventdorm.comOfficial publisherv0.2.0Updated Nov 7, 2026

Read and manage your EventDorm events, sales, attendees, and check-ins.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Remote EventDorm MCP server that lets an assistant read and manage your events, sales, attendees and check-ins.

What you can do
  • Read and manage events in your EventDorm account
  • Review sales and attendee records
  • Handle check-ins for events
  • No tool list is published, so exact actions are not documented beyond this scope.
When to use it
Useful if you run events through EventDorm and want an assistant to look up or update event details, sales, attendee lists and check-in status without switching to the dashboard.
Requirements
A remote MCP endpoint at mcp.eventdorm.com over streamable HTTP. OAuth sign-in is required, so you need an EventDorm account with access to the relevant events. No environment variables or headers are declared.
Before you install
The server can manage data, so changes to events, sales, attendees or check-ins may be written back to your EventDorm account. OAuth grants access to your account data; review the scopes requested at sign-in. No tool list is published, so verify what it can modify before use.

Installation

In SourceWeft

  1. Open EventDorm in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.eventdorm%2Feventdorm/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "eventdorm": {
      "type": "http",
      "url": "https://mcp.eventdorm.com/mcp"
    }
  }
}

README

This repository has no README.

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v0.2.0LatestNov 7, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.