Server data from the Official MCP Registry
Recordist meetings on your machine: list, search, transcripts, action items, recording control.
About
Recordist meetings on your machine: list, search, transcripts, action items, recording control.
Security Report
meetrecord is a small bridge to the local Recordist app over loopback, with no data exfiltration, shell execution, or hardcoded secrets found. Its main considerations are that the bearer token is sent to whatever RECORDIST_API_URL points to, and that unpinned npx installation and upstream error pass-through warrant attention, but neither lowers the score much. Permissions (network to the local API, token file and env var reads) match the stated purpose. Supply chain analysis found 3 known vulnerabilities in dependencies (0 critical, 2 high severity). Package verification found 1 issue.
8 files analyzed · 10 issues found
Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.
Permissions Required
This plugin requests these system permissions. Most are normal for its category.
What You'll Need
Set these up before or after installing:
How to Install
Add this to your MCP configuration file:
{
"mcpServers": {
"meetrecord": {
"command": "npx",
"args": [
"-y",
"@reneturcios/meetrecord@0.1.0"
],
"env": {
"RECORDIST_API_URL": "your-recordist-api-url-here",
"RECORDIST_DATA_DIR": "your-recordist-data-dir-here",
"RECORDIST_API_TOKEN": "your-recordist-api-token-here"
}
}
}
}Some servers take additional arguments. See the repository for details.
Documentation
View on GitHubFrom the project's GitHub README.
meetrecord
Your meetings already live on your own machine in the Recordist app. meetrecord is a small bridge to them: it talks to the app's local API (on the same machine, over loopback) and exposes nine tools for listing and searching meetings, reading transcripts, checking action items, regenerating notes, and starting or stopping a recording.
Nothing leaves the machine from meetrecord itself — every
request goes to the Recordist app, which decides what to do
with it. If the app is not running, each tool says so
plainly (Recordist app is not running) instead of guessing;
a health probe checks first, and a successful probe is
reused for five seconds so a burst of calls does not hammer
the app.
The nine tools:
list_meetings— recent meetings, with an optional full-text query,from/todate range, andlimit/offsetpaging.get_meeting— one meeting with its notes, action items, and markers.get_transcript— a meeting's transcript asjson,md,srt,vtt, ortxt(defaultmd); other values are rejected with the list of expected formats.search_meetings— full-text search across transcripts and notes; the query must be non-empty.get_action_items— action items, optionally narrowed to one meeting or to open items only.regenerate_notes— re-run AI notes for a meeting with the provider configured in Recordist, optionally with a specific notes template.start_recording— start a recording, optionally naming the source app, a title, and attendees. Recordist only honours this when "Allow agents to start recordings" is enabled in its Settings → Integrations.stop_recording— stop the current recording.add_marker— bookmark the current moment, optionally with a label.
Errors from the app come back with the app's own message when it provides one; otherwise meetrecord reports the HTTP status it saw.
Configuration
export RECORDIST_API_URL="http://127.0.0.1:47321" # default; the app on this machine
export RECORDIST_API_TOKEN="..." # optional; see below
export RECORDIST_DATA_DIR="..." # optional; where api_token lives
Authentication uses a bearer token. If
RECORDIST_API_TOKEN is set it wins; otherwise meetrecord
reads the api_token file inside RECORDIST_DATA_DIR, or
its default location
~/.local/share/app.recordist.desktop/api_token. The
health probe is the only request sent without the token.
CLI
Each tool is a subcommand taking one JSON argument string:
npx @reneturcios/meetrecord list_meetings '{"q":"budget","limit":5}'
npx @reneturcios/meetrecord get_transcript '{"meeting_id":"m123","format":"srt"}'
npx @reneturcios/meetrecord start_recording '{"title":"Weekly sync"}'
npx @reneturcios/meetrecord --version
Output is the response body the app returned. Exit codes:
0 on success, 1 on a runtime error (including a tool
error such as the app not running), 2 on a usage error.
MCP server
npx -y @reneturcios/meetrecord mcp
MCP client config:
{
"mcpServers": {
"meetrecord": {
"command": "npx",
"args": ["-y", "@reneturcios/meetrecord", "mcp"]
}
}
}
Docker
docker run -i ghcr.io/cloudcorprecords/meetrecord
docker run --rm ghcr.io/cloudcorprecords/meetrecord list_meetings '{}'
Note the container is its own machine: point
RECORDIST_API_URL at wherever the Recordist app is
reachable from the container if you run it this way.
Development
npm install
npm run build # tsc -> dist/
npm test # tsx --test test/*.test.ts (fake fetch + fake file reader + fake clock, no network)
npm run dev # run the CLI from source
License
MIT — Copyright (c) 2026 Rene Turcios
Reviews
No reviews yet
Be the first to review this server!
More Developer Tools MCP Servers
Rea
Freeby Morluto · Developer Tools
Reverse engineer anything from your terminal or agent with one CLI and MCP server.
Paperclip
Freeby Paperclipai · Developer Tools
Trending hip-hop artist momentum scores across four cultural dimensions.
Scrapling
Freeby D4Vinci · Developer Tools
Web scraping with stealth HTTP, real browsers, and Cloudflare bypass. CSS selectors supported.
Git
Freeby Modelcontextprotocol · Developer Tools
Read, search, and manipulate Git repositories programmatically
Toleno
Freeby Toleno · Developer Tools
Toleno Network MCP Server — Manage your Toleno mining account with Claude AI using natural language.
MCP Marketplace
Freeby mcp-marketplace · Developer Tools
Search and install MCP servers from inside your AI client.
