Remote MCP server that lets an assistant search and read Yappy's macOS documentation and FAQ, covering setup, permissions, LLM backends and troubleshooting.
What you can do
Search Yappy documentation and FAQ by full text, with excerpts returned for each hit, to answer how-to and troubleshooting questions such as installing Yappy, granting macOS permissions, a hotkey that does nothing, choosing an LLM backend, configuration keys, personas, or what stays on-device. Fetch a single full documentation page as markdown by slug when an excerpt is not enough, for example the complete configuration reference or the full privacy model. List every documentation page with its slug, title and one-line summary so the right page can be picked instead of guessing a slug.
When to use it
Useful when someone is setting up, configuring or troubleshooting the Yappy macOS app and wants answers grounded in its official documentation rather than general knowledge. It is a read-only documentation lookup, so it adds little outside Yappy-related questions.
Requirements
A remote streamable HTTP endpoint at yappy.biz; no package, runtime, account, API key or header is declared. Network access to that endpoint is needed.
Before you install
Read-only documentation access; no credentials, payments or write actions are declared. Answers are limited to what the published documentation and FAQ contain.
Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/biz.yappy%2Fyappy-docs/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.
Full-text search across Yappy documentation and FAQ. Use this to answer how-to and troubleshooting questions: installing Yappy, granting macOS permissions, a hotkey that does nothing, choosing an LLM backend, configuration keys, personas, or exactly what stays on-device. Results carry an excerpt you can quote and a URL you can cite.
Parameterstypelimitqueryrequired
get_documentation_page
Read a Yappy documentation page
Fetch one full Yappy documentation page as markdown, by slug. Use this after search_documentation when an excerpt is not enough and you need the whole page — for example the complete configuration reference or the full privacy model.
Parametersslugrequired
list_documentation_pages
List Yappy documentation pages
List 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.
Parametersinclude_summaries
Version history
1
v1.0.1LatestSep 16, 2026
Score
83%
83% 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 daysRequired25 pts
Auth declaredRequired10 pts
Tools listedRequired15 pts
DescriptionRequired15 pts
Logo10 pts
Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
LicenseNot applicable
A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.