EventAssets

com.eventassetsPublished by eventassets.comOfficial publisherv1.0.0Updated Nov 8, 2026

Plan and host your events: event page, guest list, RSVP, seating, agenda, budget and media.

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

Remote MCP server for planning and hosting events, covering event pages, guest lists, RSVPs, seating, agenda, budget and media.

What you can do
  • Plan and host events from start to finish
  • Manage event pages, guest lists and RSVPs
  • Handle seating arrangements and agendas
  • Track event budgets and media
When to use it
Useful when you want an assistant to help organize an event end to end — building the event page, tracking who is coming, arranging seating and agenda, and keeping budget and media in one place.
Requirements
Runs as a remote endpoint at api.eventassets.com over streamable HTTP; OAuth sign-in is required. No environment variables or headers are declared.
Before you install
The server requires OAuth authorization to an EventAssets account, so the assistant can act on your event data. It manages guest lists and RSVPs, which involve other people's personal data, and can change event details; no tool list is published, so review the granted scopes before connecting.

Installation

In SourceWeft

  1. Open EventAssets 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.eventassets%2Feventassets/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": {
    "eventassets": {
      "type": "http",
      "url": "https://api.eventassets.com/mcp"
    }
  }
}

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. v1.0.0LatestNov 8, 2026

Score

67% 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.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.