Yaps MCP
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Yaps MCPfind notes about machine learning"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Yaps connector
Use local Yaps Memory, transcription, meeting transcripts, subtitles, translation, and media conversion from Claude Desktop and other MCPB-compatible clients.
What it does
Memory: search, read, create, update, and safely delete private Markdown notes through Yaps Agent Access.
Transcription: turn local audio or video into a new plain-text transcript.
Meetings: create speaker-labelled meeting transcripts from audio or video.
Subtitles: generate a new timestamped SRT file.
Translation: translate text, Markdown, plain text, or SRT files with a local Yaps model.
Video to audio: make an MP3, WAV, or M4A copy through deterministic local conversion.
The connector deliberately excludes Yaps workflows that Anthropic does not accept in the Connectors Directory: AI text-to-speech, audio cleanup, image background removal, and rendered video captions remain available through the Yaps plugins.
Related MCP server: Obsidian MCP Server
Install
Sign in and activate an available free trial or Yaps Pro.
Open this
.mcpbfile in Claude Desktop, or install it from Settings → Extensions → Advanced settings.For Memory, open Yaps → Settings → Agent Access and allow Claude Desktop. Reads can be enabled separately from writes.
The connector finds the signed yaps_cli and yaps_mcp binaries included with Yaps. Users do not need Rust, Python, an API key, a PATH shim, or manual JSON configuration.
Safety
Every operation stays on the user's computer.
Memory uses the native Yaps Agent Access allowlist and write controls.
Note updates can reject stale overwrites; note deletion requires confirmation.
File-producing tools refuse to replace an existing file.
Read-only and write tools are separate, titled, and annotated for Claude's permission UI.
The launcher invokes only fixed Yaps commands without a shell.
Capabilities
The connector exposes 16 focused tools:
five read-only Memory tools;
three explicitly permissioned Memory write tools;
connector and feature readiness checks;
plain transcription, speaker-labelled meeting transcription, SRT generation, text translation, file translation, and deterministic video-to-audio conversion.
See TOOL_REFERENCE.md for the complete inventory.
Development
bun install --frozen-lockfile
bun run packagebun run package runs the unit suite, validates the MCPB manifest with Anthropic's official toolchain, installs production-only runtime dependencies inside the bundle, creates the .mcpb, inspects it, calculates its SHA-256 digest, and generates matching MCP Registry metadata under dist/<version>/.
The connector proxies the native Memory tools from yaps_mcp and uses the first-party yaps_cli for the other local workflows. See PUBLISHING.md for the release and directory-review gates.
Privacy Policy
Yaps' public privacy policy is at yaps.ai/privacy.
Data collection: the connector does not collect prompts, conversation history, note contents, source media, or generated files. It reads only the local paths or Yaps notes needed for the tool call the user requested.
Usage and storage: notes, source files, models, transcripts, subtitles, translations, and converted audio stay on the user's computer. The connector has no hosted proxy or analytics client.
Third-party sharing: the connector does not send tool inputs or outputs to Yaps or another third party. Claude receives the tool result required to complete the user's request.
Retention: Yaps Memory notes and generated output files remain until the user deletes them. Temporary audio created while transcribing a video meeting is deleted immediately after that tool call.
Contact: privacy and product questions can be sent to support@yaps.ai.
Support and security
Use Yaps support for product help. Follow SECURITY.md for vulnerability reports, and never attach private notes, media, transcripts, credentials, or raw Agent Access logs to a public issue.
License
MIT
This server cannot be deployed
Maintenance
Related MCP Connectors
Search and reason over your Obsidian-style Markdown vault, right from ChatGPT.
Personal context for every AI: search, read, and write back to your private Markdown library.
1Securely search and manage workspace context files for AI agents and teams.
Serve a folder of Markdown notes as an MCP server: hybrid search, reading, and sourced answers.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceEnables LLMs to read, search, and manage Obsidian vault markdown files, including YAML frontmatter, wikilinks, and graph operations through a secure stateless I/O layer.-
- FlicenseNot gradedqualityBmaintenanceProvides secure, direct file system access to Obsidian vault files, enabling search, read, write, and discovery of notes without requiring the Obsidian app.23-
- AlicenseAqualityCmaintenanceEnables AI assistants to interact with a local folder of Markdown notes, supporting listing, reading, searching, creating, and appending to notes with strict security boundaries.5MIT
- AlicenseAqualityCmaintenanceProvides read-only access to a local Obsidian vault with zero-trust security, enabling note reading, listing, and text search via Claude.36,222MIT