Presso Events

io.github.PressoNetworkPublished by GitHub account PressoNetworkv2026.1101.5Updated Nov 5, 2026

Run ticketed events from your AI assistant: create events, sell tickets via Stripe, check in.

The publisher's own server: Events.Aero

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

Remote MCP server for Presso Events that lets an assistant create ticketed events, sell tickets through Stripe and check attendees in.

What you can do
  • Create and manage ticketed events from the assistant.
  • Sell tickets through Stripe.
  • Check attendees in at an event.
  • No tool list is published, so the exact operations are not documented in the supplied material.
When to use it
Useful if you run ticketed events on Presso Events and want to set up events, sell tickets or handle check-in without leaving the assistant.
Requirements
A remote MCP endpoint at events.pressonetwork.com over streamable HTTP. OAuth authentication is required, so an account on the service is needed. No environment variables or headers are declared.
Before you install
The server can create events and sell tickets, which involves payments through Stripe and changes to real event and attendee data. OAuth grants the assistant access to your Presso Events account; review the scopes before connecting.

Installation

In SourceWeft

  1. Open Presso Events 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/io.github.PressoNetwork%2Fpresso-events/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": {
    "presso-events": {
      "type": "http",
      "url": "https://events.pressonetwork.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

3
  1. v2026.1101.5LatestNov 5, 2026
  2. v2026.1101.3Nov 1, 2026
  3. v2026.1031.0Oct 31, 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.

Other Events integrations