General Tools
yapi.work
Searches Yappy's documentation and FAQ to provide answers about installation, permissions, dictation, agent mode, LLM backend, and on-device privacy.
ENDPOINT 1
https://yapi.work
MCP server metadata
- Name
- WebMCP
Known tools 1
search_yappy_documentationSearch Yappy's documentation and FAQ for how to install it, grant macOS permissions, configure dictation, use Agent Mode, choose an LLM backend, or check what stays on-device.
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.webmcp]
url = "https://yapi.work"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"webmcp": {
"type": "http",
"url": "https://yapi.work"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: webmcp
Remote MCP URL: https://yapi.work
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": {
"webmcp": {
"url": "https://yapi.work"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"webmcp": {
"type": "http",
"url": "https://yapi.work"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "webmcp",
"transport": "streamable-http",
"url": "https://yapi.work"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.