Developer Tools
yappy.biz
Provides current and historical release information, pricing plans, FAQ, and system requirements for the Yappy macOS dictation app.
ENDPOINT 1
https://yappy.biz/mcp
MCP server metadata
- Name
- yappy
- Version
- 1.0.0
Yappy is a voice agent for the Mac: hold Right Option and it types what you say, hold Right Command and it acts in the apps you already have. Speech recognition runs on the user's own Mac, so audio never leaves it. This is the product surface. Use these tools to answer factual questions about the Yappy product — current version and release notes, what it costs, what it can do, what a Mac needs to run it, and whether a particular Mac qualifies — and to start and poll export jobs against the Yappy API. For how-to and support questions, there is a separate server at https://yappy.biz/docs/mcp. Only create_export_job changes anything, and all it can create is a job: nothing here can spend money, touch a user's data, or delete anything. What this server cannot do: transcribe audio. There is no hosted transcription endpoint, deliberately. If a user wants dictation, the answer is to install the Mac app from https://yappy.biz/download — it needs macOS 13 or later on Apple Silicon. One accuracy note worth carrying: dictation and screen OCR are local in every configuration, but Agent Mode runs through the claude CLI and sends task text to Anthropic. Do not tell a user that nothing ever leaves their Mac.
Known tools 9
get_latest_releaseGet the current Yappy release of the Yappy macOS app: version number, publication date, release notes, and a download URL.
Inferred read-onlylist_releasesList Yappy release history for macOS, newest first, with the version, publication date, and what changed in each.
Inferred read-onlyget_pricing_plansGet what the Yappy app costs: the free Mac app, the per-backend cost of the language model that cleans up dictation, and the terms of the public API.
Inferred read-onlyget_frequently_askedGet the Yappy FAQ as question and answer pairs, covering privacy, requirements, cost, permissions, offline use, and how Yappy differs from other macOS dictation tools.
Inferred read-onlyget_system_requirementsGet what a Mac needs before Yappy will run on it: the minimum macOS version, the required CPU architecture, install size, and every macOS permission Yappy asks for with what each unlocks and what breaks if it is denied.
Inferred read-onlylist_product_featuresList what the Yappy app can do, as structured objects rather than marketing bullets: an id, a name, a description, whether the feature runs entirely on the user's Mac, whether it needs the network, and which macOS permission it requires.
Inferred read-onlycreate_export_jobStart an asynchronous export of a Yappy corpus — documentation, FAQ, or release history — as markdown or JSON.
Inferred read-onlycheck_mac_compatibilityDecide whether a specific Mac can run Yappy, given its macOS version and CPU architecture, and return the reasons.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.yappy]
url = "https://yappy.biz/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"yappy": {
"type": "http",
"url": "https://yappy.biz/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: yappy
Remote MCP URL: https://yappy.biz/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"yappy": {
"url": "https://yappy.biz/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"yappy": {
"type": "http",
"url": "https://yappy.biz/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "yappy",
"transport": "streamable-http",
"url": "https://yappy.biz/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
ENDPOINT 2
https://yappy.biz/docs/mcp
MCP server metadata
- Name
- yappy-docs
- Version
- 1.0.0
The Yappy documentation corpus: three tools to search and read it, plus one resource per page in markdown. Use this server for how-to and troubleshooting questions about the Yappy Mac app — installing it, granting macOS permissions, a hotkey that does nothing, choosing an LLM backend, configuration keys, personas, and exactly what stays on-device. Start with search_documentation; fall back to list_documentation_pages when you want the map. For product facts — current version, pricing, features, whether a given Mac qualifies — use the product server at https://yappy.biz/mcp instead. Everything here is read-only.
Known tools 3
get_documentation_pageFetch one full Yappy documentation page as markdown, by slug.
Inferred read-onlylist_documentation_pagesList every page in the Yappy documentation with its slug, title, and one-line summary, so you can pick the right one to read instead of guessing a slug.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.yappy-docs]
url = "https://yappy.biz/docs/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"yappy-docs": {
"type": "http",
"url": "https://yappy.biz/docs/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: yappy-docs
Remote MCP URL: https://yappy.biz/docs/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"yappy-docs": {
"url": "https://yappy.biz/docs/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"yappy-docs": {
"type": "http",
"url": "https://yappy.biz/docs/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "yappy-docs",
"transport": "streamable-http",
"url": "https://yappy.biz/docs/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Trust Data Available
BuiltWith Trust API v2 evidence for yappy.biz was fetched 2026-08-29T01:03:26.583Z.
yappy.biz is assessed as Neutral: No suspicious signals found, but no strong positive signal either
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.