Log inSubmit server
Gateway logo

Gateway

Read, search, transcribe, and manage locally recorded Recordist meetings through MCP.

InstallRepositoryWebsite
Full README Compare alternatives Embed widget Claim this listing

Install Gateway

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "gateway-8": {
      "command": "npx",
      "args": [
        "-y",
        "@recordist/gateway"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Install not yet sandbox-tested— the server itself is confirmed live (we called its tools/list endpoint). The stdio install command is a separate, ongoing check.

Overview

The gateway MCP server connects AI assistants to meetings stored by the Recordist desktop app on the same computer. It supports meeting search, transcripts, notes, action items, recording controls, markers, and approval-based follow-up actions. Read operations can use Recordist's local API or read the database when the app is closed, while recording and other mutating operations require the app to be running. Reach for gateway when an agent needs grounded access to a person's locally captured calls without a bot joining the meeting.

Use cases

  • Search past calls for decisions or discussion points
  • Retrieve transcripts in formats such as Markdown, SRT, or VTT
  • Review open action items across recorded meetings
  • Start recordings or add markers with Recordist approval controls
  • Draft follow-ups from locally stored meeting notes

Key features

  • Local Recordist meeting access
  • Full-text search across transcripts and notes
  • Multi-format transcript retrieval
  • Recording and marker controls
  • Approval-based meeting actions
  • MCP stdio, Streamable HTTP, and A2A transports

Tools11

What Gateway lets your agent do. Expand a tool for its parameters.

Verified live~1.6k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 1d ago

Recent health check succeeded.

9/9 checks healthy over the last 38d

What it can do

From the 11 tools this server returned when we ran it; 11 declare their own safety hints.

Can delete or modify data · 2Makes network requests · 1Read-only tools · 9
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceNot published
Package age36 days
Maintainers1

Observed 2026-11-02 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 15d ago via OSV.dev · @recordist/gateway (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads1.3kPackage downloads in the last 30 days.
Last commit2d agoMost recent push to the default branch.
Tools exposed11Callable tools this server registers over MCP.
Directory activity2 viewsConfig copies, upvotes, and views on AllMCPs.

How Gateway works

What gateway does

gateway exposes Recordist's locally stored meeting data through MCP. It gives an assistant access to recent meetings, AI-generated notes, transcripts, extracted action items, markers, and full-text search results. The server communicates with the Recordist app on the local machine and listens on loopback by default.

Read access includes meeting metadata such as titles, timestamps, duration, source application, status, attendees, and tags. Agents can retrieve transcripts with speaker labels and timestamps, or request JSON, Markdown, SRT, VTT, or plain-text output. Search results include snippets, meeting identifiers, time offsets, and speakers.

The server also exposes controlled operations for active recordings and meeting follow-up. An agent can start or stop recording, add a marker, regenerate selected note types, or propose an action for approval in the Recordist app.

How it works

The default transport is MCP over stdio, launched with npx -y @recordist/gateway. When Recordist is running, gateway uses the app's local API. For read operations, it can fall back to opening recordist.db read-only when the app is closed.

Streamable HTTP is available at 127.0.0.1:47322/mcp with --http. An A2A mode is available at 127.0.0.1:47323/ with --a2a; it accepts JSON-RPC tasks and supports streaming subscriptions. HTTP and A2A requests require a bearer token from Recordist's local data directory or RECORDIST_API_TOKEN. The stdio transport does not require a token because the launching assistant is the client.

Resources are available for individual meetings and their transcripts, and the server provides prompts for summarizing a meeting, drafting a follow-up email, and conducting a weekly review.

Setup and configuration

Install or run the package with Node.js 20 or newer:

Terminal
npx -y @recordist/gateway --doctor

The diagnostic command checks the Recordist data directory, database, token, and app status. Install the Recordist desktop app for Mac, Windows, or Linux before using meeting data or app-dependent actions.

For Claude Desktop or Cursor, add the stdio command npx -y @recordist/gateway to the relevant MCP configuration. Claude Code can add it with:

Terminal
claude mcp add recordist -- npx -y @recordist/gateway

Run npx -y @recordist/gateway --http for Streamable HTTP clients. Include Authorization: Bearer <api_token> on each HTTP request.

Tools and capabilities

  • List, filter, and page through recent meetings.
  • Retrieve meeting notes, decisions, action items, markers, and transcripts.
  • Search transcripts and notes using full-text queries.
  • Filter action items by meeting or completion status.
  • Regenerate summaries, decisions, questions, follow-up emails, or custom notes.
  • Start and stop recordings and bookmark moments with markers.
  • Propose follow-up drafts, promise completion, or meeting exports for approval.
  • Check whether a proposed action is waiting, completed, failed, declined, or expired.

Limitations and notes

Recording actions, markers, note regeneration, proposals, and status checks require the Recordist app to be running. Starting a recording requires either the app setting that permits agents to start immediately or a person approving Recordist's on-screen record card. Stopping a recording is destructive and should only be done when requested.

Proposed actions do not execute immediately: Recordist displays the exact operation and waits for approval. Regenerated notes replace the current notes while earlier notes are retained by Recordist; personal notes remain intact.

The gateway communicates locally, but returned meeting content goes to the connected AI assistant and may be sent to that assistant's cloud model. Regenerated notes use the AI provider configured in Recordist, which may also be a cloud service.

Read the full README View source on GitHub

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Gateway

gateway is an MCP server that connects AI assistants to meetings recorded and stored by the Recordist desktop app. Its main tools list and search meetings, retrieve notes and transcripts, inspect action items, control recordings, add markers, regenerate notes, and propose approval-based follow-up actions.

Run `npx -y @recordist/gateway --doctor` with Node.js 20 or newer, then add `npx -y @recordist/gateway` to your MCP client configuration. The Recordist desktop app is required for app-dependent operations and should be installed on the same computer.

Yes, gateway works with Cursor through a stdio MCP configuration. Add an `mcpServers` entry that runs `npx -y @recordist/gateway` in `.cursor/mcp.json` for a project or in the global Cursor configuration.

Yes, read operations can work while Recordist is closed. gateway falls back to opening Recordist's `recordist.db` in read-only mode, while recording controls, markers, note regeneration, and other app-dependent actions require the desktop app to be running.

Recording starts immediately only when Recordist's agent-start setting is enabled; otherwise the app shows its own record card and waits for the person to respond. Proposed follow-up actions always appear in an approval card and run only after the person selects Approve.

Related MCP servers

All in Workplace & Productivity All alternatives
Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewGateway AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/gateway-8?style=directory)](https://allmcps.com/mcp/gateway-8)
HTML Embed
<a href="https://allmcps.com/mcp/gateway-8"><img src="https://allmcps.com/api/badge/gateway-8?style=directory" alt="Gateway on AllMCPs" /></a>