Gateway

app.recordistPublished by recordist.appv0.1.10Updated Nov 10, 2026

Read, search and act on meetings Recordist recorded locally. Listens on loopback by default.

Overview

AI-generated overview

Bridges an AI assistant to the local Recordist meeting recorder: list, search and read meetings, transcripts and action items, and control recordings.

What you can do
  • List, fetch and full-text search meetings, with notes, action items and markers
  • Read a meeting transcript as json, md, srt, vtt or txt with speakers and timestamps
  • List action items, filtered by meeting or open only
  • Start and stop recordings and add markers in the active recording
  • Regenerate AI notes and propose follow-up drafts, promise updates or exports for the person to approve
  • Check the status of a proposed action
When to use it
Useful when you want an assistant to answer questions from your own recorded calls and meetings, pull out open action items, draft follow-ups, or start and stop recording from the assistant. Reads work even with the Recordist app closed; recording controls need it running.
Requirements
Local stdio process run with npx, requiring Node 20+ and the Recordist desktop app installed (Mac, Windows or Linux). Reads fall back to the local recordist.db when the app is closed; actions need the app running. Optional environment variables RECORDIST_DATA_DIR, RECORDIST_API_URL and RECORDIST_API_TOKEN; the HTTP and A2A modes require a bearer token.
Before you install
Meeting transcripts and notes returned to the assistant may be sent to its cloud model, so connect only an assistant you trust with them. stop_recording and regenerate_notes are destructive and replace current notes; start_recording may begin at once if the person enabled agent recordings. The api_token controls recording on the machine and must not be shared; do not expose the HTTP or A2A modes on a network interface.

Installation

In SourceWeft

  1. Open Gateway in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

@recordist/gateway

[Listed on mcpservers.org] [Glama score]

MCP server + A2A agent for Recordist (https://recordist.app), the app that writes notes from your calls on-device, with no bot in the call. It lets Claude Desktop, Claude Code, Cursor and other agents read and act on the meetings you recorded, where they are kept.

Get the free Recordist app for Mac, Windows and Linux: https://recordist.app/download?from=npm

  • Reads (list, get, transcript, search, action items) work whether or not the Recordist app is running: the gateway talks to the app's local API when it is up and falls back to opening recordist.db read-only when it is not.
  • Actions (start and stop recording, add a marker, regenerate notes) need the app. When it is not running they fail with Recordist app is not running.
  • Recording asks first. start_recording starts at once only when Allow agents to start recordings is on in Recordist's Settings, then Integrations (off by default). Otherwise Recordist shows its own record card on screen, as it does for the Chrome extension and Stream Deck, and nothing records until the person answers it. Recordist 1.0.4 and earlier show that card only while the Chrome extension switch is on in Settings, then Detection; with both off, the agent is told the recording did not start and the person can start it in Recordist. stop_recording and regenerate_notes are marked destructive, so assistants that honour MCP's hints ask each time.
  • Where your meetings go. The gateway itself talks only to the Recordist app on 127.0.0.1 and listens on loopback by default. What it returns goes to the AI assistant you connect, which may send it to its own cloud model. regenerate_notes has the app write notes with the provider set in Recordist's Settings → AI notes, which may also be a cloud service.

Install

bash
npx -y @recordist/gateway --doctor     # check data dir, DB, token, app

Requires Node 20+. better-sqlite3 ships prebuilt binaries for common platforms.

Connect an assistant

Claude Desktop: the extension

The Recordist extension installs in Claude Desktop in one step and needs no configuration. Double-click recordist-<version>.mcpb (build it as in Claude Desktop Extension), or in Claude Desktop open Settings → Extensions → Advanced settings → Install Extension… and choose the file. Claude shows what the extension can do before you install it.

Claude Desktop: by hand

claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\):

json
{  "mcpServers": {    "recordist": {      "command": "npx",      "args": ["-y", "@recordist/gateway"]    }  }}

Claude Code

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

or, for the HTTP transport while npx -y @recordist/gateway --http is running (it needs the app's API token, see Authentication):

bash
TOKEN="$(cat ~/Library/Application\ Support/app.recordist.desktop/api_token)"claude mcp add --transport http recordist http://127.0.0.1:47322/mcp \  --header "Authorization: Bearer $TOKEN"

Claude Code plugin

This repository is also a Claude Code plugin marketplace. The plugin in plugins/recordist starts this gateway, pinned to a published version, and adds a skill for answering from the record:

/plugin install recordist --marketplace recordist-app/gateway

On Claude Code before 2.1.275, add the marketplace first: /plugin marketplace add recordist-app/gateway, then /plugin install recordist@recordist.

Cursor

.cursor/mcp.json (project) or ~/.cursor/mcp.json (global):

json
{  "mcpServers": {    "recordist": {      "command": "npx",      "args": ["-y", "@recordist/gateway"]    }  }}

Any Streamable HTTP client

bash
npx -y @recordist/gateway --http          # http://127.0.0.1:47322/mcp

Send Authorization: Bearer <api_token> with every request.

Authentication

The HTTP transport (--http) and the A2A agent (--a2a) answer only requests that carry Authorization: Bearer <api_token>, where the token is the contents of <data>/api_token (or RECORDIST_API_TOKEN), the same token the gateway uses for the app's local API. A missing or wrong token gets 401 with WWW-Authenticate: Bearer and nothing else. The one exception is the A2A Agent Card, which stays public so clients can discover the scheme; it lists skills only, never meetings. Neither mode starts when no token is available, and neither does --all, stdio included: open Recordist once so it writes api_token, or run with no flags for stdio alone. The stdio transport needs no token, since only the assistant that launched it can talk to it. --doctor says whether --http and --a2a will require the token or refuse to start.

What the assistant gets

Tools

ToolPurpose
list_meetingsRecent meetings; optional q, from/to, limit/offset
get_meetingOne meeting with notes, action items and markers
get_transcriptTranscript as json | md | srt | vtt | txt
search_meetingsFull-text search across transcripts and notes (FTS5)
get_action_itemsAction items, filter by meeting_id / open_only
regenerate_notesWrite the AI notes again (summary, action_items, decisions, …) with the provider set in Recordist; they replace the current notes, which Recordist keeps under Earlier notes (destructive); needs the app
start_recordingRecord: starts at once with Allow agents to start recordings on (Settings → Integrations, off by default), otherwise shows Recordist's record card for the person to answer; needs the app
stop_recordingStop the recording under way (destructive: hosts ask first); needs the app
add_markerBookmark the current moment; needs the app
propose_actionRecordist Agent: suggest an action on the record (draft the follow-up, mark a promise done, export a meeting). Nothing runs: the app shows a card that says exactly what will happen and waits for the person's Approve or Not now; needs the app and Let connected assistants suggest actions in Settings → Integrations → Recordist Agent
action_statusWhat became of a suggestion: proposed, done, failed, declined or expired, and nothing more; needs the app

Resources: recordist://meeting/{id} (JSON) and recordist://meeting/{id}/transcript (Markdown). The resource list shows the 50 most recent meetings.

Prompts: summarize_meeting, draft_followup_email, weekly_review.

A2A agent

bash
npx -y @recordist/gateway --a2a           # http://127.0.0.1:47323/

Agent Card at http://127.0.0.1:47323/.well-known/agent.json (public, no token; authentication.schemes is ["bearer"]); skills mirror the tools above. JSON-RPC 2.0 at / with tasks/send, tasks/get, tasks/cancel and tasks/sendSubscribe (SSE); every JSON-RPC request needs Authorization: Bearer <api_token>.

Natural-language tasks are routed to a skill with a small keyword router; every completed task returns a text part and a data part with the structured result. To skip the router, send a data part {"skill": "...", "args": {...}}.

bash
TOKEN="$(cat ~/Library/Application\ Support/app.recordist.desktop/api_token)"
curl -s http://127.0.0.1:47323/ \  -H "Authorization: Bearer $TOKEN" \  -H 'content-type: application/json' \  -d '{    "jsonrpc": "2.0", "id": 1, "method": "tasks/send",    "params": {      "id": "task-1",      "message": { "role": "user", "parts": [        { "type": "text", "text": "What are my open action items from this week?" }      ]}    }  }' | jq .result.artifacts[0].parts
# explicit skill callcurl -s http://127.0.0.1:47323/ -H "Authorization: Bearer $TOKEN" -H 'content-type: application/json' -d '{  "jsonrpc":"2.0","id":2,"method":"tasks/send",  "params":{"message":{"role":"user","parts":[    {"type":"data","data":{"skill":"get_transcript","args":{"meeting_id":"01J…","format":"srt"}}}  ]}}}'
# streamingcurl -N http://127.0.0.1:47323/ -H "Authorization: Bearer $TOKEN" -H 'content-type: application/json' -d '{  "jsonrpc":"2.0","id":3,"method":"tasks/sendSubscribe",  "params":{"message":{"role":"user","parts":[{"type":"text","text":"list my meetings from today"}]}}}'

CLI

npx -y @recordist/gateway                 MCP over stdio (default)npx -y @recordist/gateway --http          MCP over Streamable HTTP on 127.0.0.1:47322/mcp (bearer token)npx -y @recordist/gateway --a2a           A2A agent on 127.0.0.1:47323 (bearer token)npx -y @recordist/gateway --all           stdio + --http + --a2a (exits if there is no token)npx -y @recordist/gateway --doctor        diagnostics: data dir, DB, token, app reachability, HTTP/A2A authnpx -y @recordist/gateway --version  --http-port <n>  --a2a-port <n>  --host <addr>

Always run it with npx by its scoped name, @recordist/gateway. A global install (npm i -g @recordist/gateway) puts the same command on your path as recordist-gateway.

--host binds --http and --a2a to another address and exists for containers. Do not expose it on a network interface: the token would cross the network in plain HTTP.

Logs go to stderr; stdout is reserved for the stdio MCP transport.

Environment variables

VariableDefaultPurpose
RECORDIST_DATA_DIRmacOS ~/Library/Application Support/app.recordist.desktop
Windows %LOCALAPPDATA%\app.recordist.desktop
Linux ~/.local/share/app.recordist.desktop
Where recordist.db and api_token live
RECORDIST_API_URLhttp://127.0.0.1:47321Local API base URL
RECORDIST_API_TOKENcontents of <data>/api_tokenBearer token for the local API, and the token --http and --a2a require from callers

How backend selection works

On each call the gateway probes GET /v1/health (800 ms timeout, result cached for 5 s). If the app answers, the call goes to the API. Otherwise reads open <data>/recordist.db read-only (the app's WAL is never written to) and actions return Recordist app is not running. The database is opened with better-sqlite3 when its native binary matches the Node that runs the gateway, and with node:sqlite (Node 22.13 and later) when it does not. If neither can open it, the error says why for each. FTS5 (segments_fts) is used for search when present, with a LIKE fallback otherwise.

Security notes

  • The gateway binds 127.0.0.1 by default. --host exists for containers; do not expose it on a network interface. The Streamable HTTP transport enables DNS-rebinding protection and only accepts its own Host (127.0.0.1 or localhost by default). The A2A agent accepts only its own Host, no browser Origin unless allow-listed, and JSON-RPC POSTs only as application/json.
  • The gateway itself talks only to the Recordist app on 127.0.0.1. What it returns goes to the AI assistant you connect, which may send it to its own cloud model, so connect only an assistant you trust with your meetings.
  • --http and --a2a require Authorization: Bearer <api_token> on every request (the A2A Agent Card excepted), compared in constant time, so other user accounts on the machine cannot read meetings through them. Programs running under your own account can read api_token, so the token does not separate them from you.
  • The API token is read from <data>/api_token, which the app writes with mode 0600. --doctor warns if the file is group/world readable. Never commit or share it; anyone with the token can control recording on that machine.
  • The SQLite database is opened read-only; the gateway never modifies it.
  • No telemetry. The gateway makes no network calls other than to the Recordist app's local API.

Privacy

The gateway and the extension talk to the Recordist app on the same machine, on 127.0.0.1, and to nothing else. They send nothing to Recordist and have no telemetry. What a tool returns goes to the assistant that called it, which may send it to its own cloud model under its provider's terms. Recordist's privacy policy: https://recordist.app/privacy

Claude Desktop Extension

mcpb/manifest.json describes the extension in the MCP Bundle format. Build it with:

bash
npm cibash scripts/build-mcpb.sh      # build/recordist-<version>.mcpb

The script compiles the gateway, installs the production dependencies at their locked versions, leaves out better-sqlite3 so the bundle carries no native code, then validates and packs it with the official @anthropic-ai/mcpb CLI. Claude Desktop runs the extension with the Node it ships, so reads with Recordist closed use node:sqlite.

Changes in 0.1.10

  • On Windows the gateway finds your meetings without RECORDIST_DATA_DIR: it reads %LOCALAPPDATA%\app.recordist.desktop, where the Windows app keeps them (0.1.9 and earlier looked in %APPDATA%).

Changes in 0.1.9

  • The README says what Recordist is today: on Mac, Windows and Linux, notes written on-device.

Changes in 0.1.8

  • The Claude Desktop Extension: mcpb/manifest.json, mcpb/icon.png and scripts/build-mcpb.sh, which builds recordist-<version>.mcpb.
  • A Claude Code plugin in plugins/recordist, listed by the marketplace in .claude-plugin/marketplace.json.
  • Reads with the app closed fall back to node:sqlite when better-sqlite3 cannot load, for example under a Node it was not built for. When neither can open recordist.db, the error names the reason for each instead of saying the file was not found.
  • A 0.1.7 setup works as it is: the transports, the token checks and the tool names are unchanged.
  • start_recording no longer just fails while Allow agents to start recordings is off (the default): it asks Recordist to show its own record card, and says that nothing records until the person answers it. "Record this call" now works with the safe default.
  • stop_recording and regenerate_notes carry destructiveHint, so hosts ask before ending a recording or replacing the notes.
  • stop_recording waits 30 seconds for the app (it answers once the last of the transcript is written) and, if no answer comes, asks the app again: a recording that has ended is reported as stopped, not as an error.
  • Plain error words, and the README points to the download page instead of the early-access waiting list, which has closed.

Changes in 0.1.7

  • Security: dependency updates for advisories in @modelcontextprotocol/sdk and transitive packages. The SDK floor is now 1.31.0, the first version with the fix for GHSA-6qxp-vccf-f47h. Tools, transports and token checks are unchanged, so a 0.1.6 setup works as it is.

Changes in 0.1.6

  • The README and the package and plugin descriptions now say where meeting text goes. The gateway itself talks only to the Recordist app on 127.0.0.1 and listens on loopback by default. What it returns goes to the AI assistant you connect, which may send it to its own cloud model. Earlier versions said that nothing leaves your machine. That is true of the gateway alone, and a cloud assistant sends what it reads to its provider.
  • The README says the gateway binds 127.0.0.1 by default and that --host is for containers, where it used to say the gateway only ever binds 127.0.0.1.
  • The Recordist app is described as available for Macs with Apple silicon, which is the only build published.
  • start_recording names the setting as the app shows it: Allow agents to start recordings, in Settings → Integrations.
  • Every command in the README and in --help uses the scoped name, npx -y @recordist/gateway.
  • Source comments point to the public local API reference.
  • Tools, transports and token checks are unchanged, so a 0.1.5 setup works as it is.

Changes in 0.1.5

  • --http and --a2a now require Authorization: Bearer <api_token> on every request; a missing or wrong token gets 401. The A2A Agent Card stays public and now lists authentication.schemes: ["bearer"]. If you used either mode, add the header to your client (see Authentication). The stdio transport is unchanged.
  • --http and --a2a refuse to start when no token is available (<data>/api_token missing and RECORDIST_API_TOKEN unset). So does --all, and it exits before stdio starts, so an assistant that launches the gateway with --all gets nothing. Without a token, launch it with no flags (stdio only).
  • Library: createMcpHttpServer and createA2AServer now take a required token option (the app's api_token) and throw when it is missing or blank. Pass loadConfig().apiToken, as in Library use.
  • --doctor reports whether --http and --a2a will require the token or refuse to start, and where the token comes from.
  • The MCP HTTP transport answers 400 to an unparsable request path instead of ending the process (the A2A agent already did since 0.1.3).

Development

bash
npm installnpm run build      # tsc → dist/npm test           # vitestnode dist/cli.js --doctor

Library use

ts
import { createRecordistData, createMcpServer } from "@recordist/gateway";
const data = createRecordistData();          // API with SQLite fallbackconst server = createMcpServer(data);        // McpServer; attach any transport

The HTTP and A2A servers require a bearer token and throw without one:

ts
import { createMcpHttpServer, createMcpServer, createRecordistData, listen, loadConfig } from "@recordist/gateway";
const config = loadConfig();                 // apiToken: <data>/api_token or RECORDIST_API_TOKENif (!config.apiToken) throw new Error("open Recordist once so it writes api_token");const data = createRecordistData(config);const http = createMcpHttpServer({  createServer: () => createMcpServer(data),  token: config.apiToken,                    // callers must send Authorization: Bearer <token>});await listen(http, 47322);

About

The gateway is the small, open bridge between your AI assistant and the copy of Recordist running on your own machine. It contains no app code and no keys; it can only reach the local API on the machine it runs on. Issues and questions: [email protected]. Security reports: [email protected] (see SECURITY.md). Made by Recordist, a small independent studio in Ontario, Canada.

Source: README.md at commit 8b17411

Tools

11

list_meetings

List meetings

List recent meetings captured by Recordist, newest first. Optional full-text filter `q`, a date range (`from`/`to`) and paging (`limit`/`offset`). Returns id, title, start time, duration, source app, status, attendees and tags.

Parametersqtofromlimitoffset

get_meeting

Get meeting

Fetch one meeting by id including its AI notes (summary, decisions, …), action items and markers. Use `get_transcript` for the full transcript.

Parametersmeeting_idrequired

get_transcript

Get transcript

Return a meeting's transcript. `format` is one of json (segments with ms timestamps), md, srt, vtt or txt (default md). Speaker labels and timestamps are included.

Parametersformatmeeting_idrequired

search_meetings

Search meetings

Full-text search across all transcripts and notes. Returns matching snippets with the meeting id, title, time offset and speaker so you can jump to the moment.

Parameterslimitqueryrequired

get_action_items

Get action items

List action items extracted from meetings. Filter by `meeting_id` and/or `open_only` (exclude completed items).

Parameterslimitopen_onlymeeting_id

regenerate_notes

Regenerate notes

Ask the Recordist app to write a meeting's AI notes again. They replace the current notes and open action items (Recordist keeps the earlier ones under Earlier notes; the person's own notes stay). `kind` is summary, action_items, decisions, questions, followup_email or custom; `template_id` selects a template. Requires the app to be running.

Parameterskindmeeting_idrequiredtemplate_id

start_recording

Start recording

Record a meeting via the Recordist app. If the person turned on 'Allow agents to start recordings' in Recordist (Settings, Integrations), the recording starts at once. Otherwise, the safe default, Recordist shows its own record card on the person's laptop and nothing records until they answer it; the result says which happened. Requires the app to be running.

Parameterstitlesource_app

stop_recording

Stop recording

Stop the recording under way. This ends the person's recording of their call, so only stop it when they ask you to. Transcription and notes continue in the background. Requires the app to be running.

Takes no parameters.

add_marker

Add marker

Bookmark the current moment in the active recording with an optional label. Requires the app to be running.

Parameterslabel

propose_action

Suggest an action

Suggest an action on the person's record for them to approve in the Recordist app: draft the follow-up (kind draft_followup: meeting_id, optional template_id), mark a promise done (kind mark_promise_done: action_item_id), or export a meeting (kind export_meeting: meeting_id, optional format md|txt|srt|vtt|json). Nothing runs on this call. Recordist shows a card that says exactly what will happen and waits for the person to press Approve or Not now; a suggestion nobody answers runs out. Use `reason` to say why, in one sentence; it is shown on the card in your words. Poll `action_status` for the answer. Requires the app to be running and 'Let connected assistants suggest actions' turned on in Settings → Integrations → Recordist Agent.

Parametersviakindrequiredformatreasonmeeting_idtemplate_idaction_item_id

action_status

What became of a suggestion

The status of an action you suggested with propose_action: proposed (waiting), done, failed, declined (the person said Not now) or expired (nobody answered in time). Only the status and the time of the answer come back; the card's words and any result stay in the app. Requires the app to be running.

Parametersidrequired

Version history

6
  1. v0.1.10LatestNov 3, 2026
  2. v0.1.8Oct 29, 2026
  3. v0.1.7Oct 13, 2026
  4. v0.1.6Oct 8, 2026
  5. v0.1.5Oct 8, 2026
  6. v0.1.2Sep 27, 2026

Score

90% 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 days25 pts
  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts