Local MCP server/Productivity

VOMO MCP server

Local MCP server

VOMO finds and reads meeting notes, summaries and original transcripts through a local MCP server. Install the global CLI, run vomo auth login, then run vomo mcp serve and add that local command to your client. Access is read-only and uses the existing VOMO account session. Node.js 18+ and a VOMO account are required; the server lists tools even when signed out, but calls fail until you sign in.

OAuth Local install path Reviewed 2026-11-16
About

Where it fits

VOMO users who want meeting notes and transcripts available to a local AI client.

  • Find meeting notes by topic.
  • Read a VOMO meeting summary.
  • Open the original meeting transcript.

A remote MCP server advertises tools to your client. The provider controls the tools, the data they can reach, and the permissions they need. Read the provider's docs before you use it with private data.

Install

Local CLI and stdio server

Requires Node.js 18+ and a VOMO account. Run vomo auth login before vomo mcp serve; the server lists tools even when signed out, but calls fail until you authenticate.

  1. Install the global CLI

    Install the provider CLI and confirm vomo is on PATH. Node.js 18+ is required.

    npm install -g @vomoai/cli
  2. Sign in

    Authenticate with the existing VOMO account session.

    vomo auth login
  3. Start the stdio server

    Run the local MCP server and add that command to your client.

    vomo mcp serve
  4. Confirm access

    List one note to verify the signed-in session works.

    vomo notes list --limit 1

This is a local install path. Install and run it first, then add the local command or URL to OpenCode, VS Code, or another compatible client. The provider controls the package, required keys, and runtime.

Troubleshooting

Common failure modes

These are the problems to check first. If the provider changes its endpoint or authentication flow, use its documentation as the source of truth.

  • The sign-in window closes without returning. Allow pop-ups and finish the provider login in the same browser.
  • The server connects but its tools are missing. Remove it, add it again, and approve the scopes the provider lists.
  • The client cannot find the vomo command. Confirm the global CLI install and that the executable is on PATH.
  • The process starts but no tools appear. Sign in to the provider CLI, restart the client, and check the local command output for errors.
Safety

Before you connect

Local process, your machine
  • The MCP server process runs on your machine, not on a provider host.
  • Data leaves only through the model provider and any MCP servers you attach.
  • Review the local command, package, and files it can reach before running it.
  • Stop the process or remove the client entry when you no longer need it.
Review path

Check the connection before a real task

These guides cover the decisions that a provider description cannot answer: endpoint ownership, scopes, tool access, and a read-only test.

Reference

Provider documentation

Setup requirements, available tools, and rate limits live with the provider. Use the source link as the authority for this server.

VOMO documentationhttps://vomo.ai/cliGitHub repositoryhttps://github.com/Vomo-ai/vomo-skill