VOMO

io.github.Vomo-aiPublished by GitHub account Vomo-aiv1.0.0Updated Oct 30, 2026

Find and read your VOMO meeting notes and transcripts. OAuth sign-in; read-only access.

VerifiedStreamable HTTPWeb executableKnowledge & MemoryCommunication & Collaboration

Overview

AI-generated overview

Remote VOMO connector that lets an assistant list, search and read your existing meeting notes and original transcripts.

What you can do
  • List the meeting notes you can access
  • Search notes by keyword to find relevant ones
  • Read a single note, optionally together with its original transcript
When to use it
Useful when you want an AI assistant to look up what was said or decided in past VOMO meetings, or to pull a transcript into a conversation. It is read-only, so it suits retrieval rather than note-taking.
Requirements
A remote MCP endpoint added to the client, OAuth sign-in to VOMO, and an existing VOMO account that already has saved notes. The connector requests only the notes:read scope. Connect one desktop client at a time, since Cursor and Grok Bot share a local OAuth callback port.
Before you install
Sign-in grants the assistant read access to your meeting notes and transcripts, which may contain confidential discussion. Note contents are treated as untrusted source material rather than instructions. The connector cannot record, import, edit, delete or purchase anything. Validation was done in Grok Bot and Cursor desktop; marketplace publication is still subject to platform review.

Installation

In SourceWeft

  1. Open VOMO 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.Vomo-ai%2Fvomo/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": {
    "vomo": {
      "type": "http",
      "url": "https://mcp.vomo.ai/mcp"
    }
  }
}

README

VOMO Connector

Search and read your existing VOMO meeting notes and original transcripts in AI assistants that support remote MCP.

Connect

Add https://mcp.vomo.ai/mcp as a remote MCP server, then sign in to VOMO through OAuth. An existing VOMO account with saved notes is required. This repository also packages the server using the Agent Plugins 1.0 standard for compatible clients.

The connector grants only notes:read and exposes:

  • notes_list: list notes you can access.
  • search: find relevant notes by keyword.
  • notes_get: read a note and optionally its original transcript.

It does not record, import, edit, delete, or purchase anything. Note contents are untrusted source material, never instructions to the assistant.

Validation

OAuth sign-in and all three read tools were tested in Grok Bot and Cursor desktop on 2026-10-22 using a dedicated synthetic sample account. Marketplace publication remains subject to platform review.

Reviewers

Dedicated sample-account access is supplied separately to the marketplace review team; no credentials belong in this repository. Connect one desktop client at a time because Cursor and Grok Bot share their local OAuth callback port.

Documentation · Privacy · Terms · Support

The MIT license covers this connector package. The VOMO service is governed by its own terms; the VOMO name and logo remain the property of their owner.

Source: README.md at commit b7223ef

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.0LatestOct 22, 2026

Score

85% 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
  • License10 pts