app.recordist由 recordist.app 发布v0.1.10更新于 Nov 7, 2026
读取、搜索并处理Recordist在本地录制的会议。默认监听回环地址。
AI 翻译由 AI 模型根据下方的原文描述翻译，可能有误。
Read, search and act on meetings Recordist recorded locally. Listens on loopback by default.
Gateway 的本地 MCP 服务，由 recordist.app 发布；无需登录；STDIO；11 个工具。
暂无 AI 概览：以下信息来自注册中心条目和服务本身。
Desktop only，通过 STDIO。 STDIO 服务会启动本地进程，因此需要 SourceWeft 桌面宿主。
参照 仓库 中的启动说明。
[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
recordist.db read-only when it is not.Recordist app is not running.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.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.Requires Node 20+. better-sqlite3 ships prebuilt binaries for common platforms.
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_config.json (macOS: ~/Library/Application Support/Claude/,
Windows: %APPDATA%\Claude\):
or, for the HTTP transport while npx -y @recordist/gateway --http is running (it needs
the app's API token, see Authentication):
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:
On Claude Code before 2.1.275, add the marketplace first:
/plugin marketplace add recordist-app/gateway, then
/plugin install recordist@recordist.
.cursor/mcp.json (project) or ~/.cursor/mcp.json (global):
Send Authorization: Bearer <api_token> with every request.
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.
Tools
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.
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": {...}}.
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.
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.
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.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.<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 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
mcpb/manifest.json describes the extension in the
MCP Bundle format. Build it with:
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.
RECORDIST_DATA_DIR: it reads %LOCALAPPDATA%\app.recordist.desktop, where the Windows app keeps them (0.1.9 and earlier looked in %APPDATA%).mcpb/manifest.json, mcpb/icon.png and
scripts/build-mcpb.sh, which builds recordist-<version>.mcpb.plugins/recordist, listed by the marketplace in
.claude-plugin/marketplace.json.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.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.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.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.start_recording names the setting as the app shows it: Allow agents to
start recordings, in Settings → Integrations.--help uses the scoped name,
npx -y @recordist/gateway.--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).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.400 to an unparsable request path instead of
ending the process (the A2A agent already did since 0.1.3).The HTTP and A2A servers require a bearer token and throw without one:
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.
来源：README.md，提交 8b17411
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.
qtofromlimitoffsetGet meeting
Fetch one meeting by id including its AI notes (summary, decisions, …), action items and markers. Use `get_transcript` for the full transcript.
meeting_id必填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.
formatmeeting_id必填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.
limitquery必填Get action items
List action items extracted from meetings. Filter by `meeting_id` and/or `open_only` (exclude completed items).
limitopen_onlymeeting_idRegenerate 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.
kindmeeting_id必填template_idStart 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.
titlesource_appStop 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.
无需输入参数。
Add marker
Bookmark the current moment in the active recording with an optional label. Requires the app to be running.
labelSuggest 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.
viakind必填formatreasonmeeting_idtemplate_idaction_item_idWhat 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.
id必填已满足适用检查项的 90%
该评分衡量此收录条目的完整程度，依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价，也不表示服务器安全或当前可用：可连通性是带日期的检查结果，评分也不包含安装量或用户评价。
请在注册中心条目中声明凭据请求头，或保持端点能够响应探测，以便判定其认证方式。
npx -y @recordist/gateway --doctor # check data dir, DB, token, app{ "mcpServers": { "recordist": { "command": "npx", "args": ["-y", "@recordist/gateway"] } }}claude mcp add recordist -- npx -y @recordist/gatewayTOKEN="$(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"/plugin install recordist --marketplace recordist-app/gateway{ "mcpServers": { "recordist": { "command": "npx", "args": ["-y", "@recordist/gateway"] } }}npx -y @recordist/gateway --http # http://127.0.0.1:47322/mcpnpx -y @recordist/gateway --a2a # http://127.0.0.1:47323/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"}]}}}'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>npm cibash scripts/build-mcpb.sh # build/recordist-<version>.mcpbnpm installnpm run build # tsc → dist/npm test # vitestnode dist/cli.js --doctorimport { createRecordistData, createMcpServer } from "@recordist/gateway";
const data = createRecordistData(); // API with SQLite fallbackconst server = createMcpServer(data); // McpServer; attach any transportimport { 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);