Manymeet

io.github.jmbremerPublished by GitHub account jmbremerv1.0.0Updated Oct 24, 2026

Webinar analytics for Zoom Meeting-based webinars: Funnels, transcripts, email engagement

VerifiedStreamable HTTPWeb executableCommunication & CollaborationData & Analytics

Overview

AI-generated overview

A remote MCP server from Manymeet that gives an assistant access to webinar analytics for Zoom Meeting-based webinars, including funnels, transcripts and email-

What you can do
The manifest lists no tools, so capabilities are inferred from the description: it covers webinar analytics for webinars run on Zoom Meetings, spanning funnels, transcripts and email engagement. An assistant could use it to look up how a webinar performed and what was said or sent around it. No tool-level detail is published.
When to use it
Useful when you want an assistant to work with performance and engagement data from Zoom Meeting-based webinars, such as reviewing funnel results, transcripts or email engagement, rather than general Zoom meeting management.
Requirements
A remote endpoint at app.getmanymeet.com over streamable HTTP. OAuth authentication is required, so a Manymeet account with the relevant webinar data is needed. No environment variables or headers are declared.
Before you install
Access is granted through OAuth to a third-party service, so review the scopes requested and what webinar, transcript and email engagement data is shared with it. The manifest lists no tools, so what the assistant can read or change cannot be verified in advance.

Installation

In SourceWeft

  1. Open Manymeet 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.jmbremer%2Fmanymeet/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": {
    "manymeet": {
      "type": "http",
      "url": "https://app.getmanymeet.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.0LatestSep 16, 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.