EventWave

io.github.jgaethle10Published by GitHub account jgaethle10v1.0.2Updated Oct 24, 2026

Event discovery and promotion workflows with human-controlled publishing and commerce.

The publisher's own server: Wave AI

VerifiedStreamable HTTPWeb executableProductivity & Workflow

Overview

AI-generated overview

EventWave is a remote MCP endpoint for event discovery and promotion workflows, with publishing and commerce kept under human control.

What you can do
Discover events and gather event information for promotion workflows, as described for the service. Prepare promotion and commerce steps while leaving publishing decisions to a person. No tool list is published, so the exact actions an assistant can take are not documented here.
When to use it
Consider it when you want an assistant to help find events and prepare promotion or commerce work, while a person approves what actually gets published.
Requirements
A remote streamable HTTP endpoint; the assistant connects to the hosted address directly. No packages, environment variables, headers or authentication are declared, so no local runtime or credentials are documented.
Before you install
Publishing and commerce are involved; the description says publishing is human-controlled, so confirm what the assistant can change or send before relying on it. No authentication is declared, so check how access is protected. The tool list is unpublished, so verify its actual capabilities first.

Installation

In SourceWeft

  1. Open EventWave in the dashboard and add it to a workspace.
  2. 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.jgaethle10%2Feventwave/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.

{
  "mcpServers": {
    "eventwave": {
      "type": "http",
      "url": "https://event-wave.base44.app/functions/eventWaveMcp"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

2
  1. v1.0.2LatestSep 25, 2026
  2. v1.0.0Sep 24, 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 listedRequired15 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 Wave integrations