YawLabs

io.github.YawLabsPublished by GitHub account YawLabsv1.1.16Updated Nov 21, 2026

MCP gateway: one local install fronts every MCP server for Claude Code, Cursor, and VS Code.

VerifiedSTDIODesktop onlyDeveloper Tools

Overview

AI-generated overview

A local MCP gateway that fronts every MCP server behind one install for Claude Code, Cursor and VS Code.

What you can do
  • Acts as a single local gateway in front of multiple MCP servers.
  • Lets coding assistants such as Claude Code, Cursor and VS Code reach those servers through one install.
  • No individual tools are documented in the supplied listing, so the exact capabilities depend on the servers it fronts.
When to use it
Worth considering if you use several MCP servers across Claude Code, Cursor or VS Code and want to manage them through one local install instead of configuring each separately.
Requirements
Runs as a local process on the user's machine over stdio, installed from the npm package @yawlabs/mcp, so a Node.js runtime is needed. Desktop only; no authentication, environment variables or headers are declared.
Before you install
It sits in front of other MCP servers, so the tools, credentials and data access of those servers pass through it; review what it fronts before installing. No tool list, README or instructions were provided, so its behavior cannot be verified from this listing.

Installation

In SourceWeft

  1. Open YawLabs in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

29
  1. v1.1.16LatestNov 21, 2026
  2. v1.1.15Nov 19, 2026
  3. v1.1.13Nov 14, 2026
  4. v1.1.12Nov 13, 2026
  5. v1.1.11Nov 12, 2026
  6. v1.1.10Nov 11, 2026
  7. v1.1.9Nov 5, 2026
  8. v1.1.8Nov 4, 2026
  9. v1.1.7Nov 3, 2026
  10. v1.1.6Oct 31, 2026
  11. v1.1.5Oct 31, 2026
  12. v1.1.4Oct 22, 2026
  13. v1.1.2Oct 20, 2026
  14. v1.1.1Oct 17, 2026
  15. v1.1.0Oct 12, 2026
  16. v1.0.20Oct 6, 2026
  17. v1.0.19Oct 4, 2026
  18. v1.0.18Oct 1, 2026
  19. v1.0.17Sep 29, 2026
  20. v1.0.16Sep 25, 2026
  21. v1.0.15Sep 25, 2026
  22. v1.0.13Sep 24, 2026
  23. v1.0.12Sep 23, 2026
  24. v1.0.11Sep 22, 2026
  25. v1.0.10Sep 21, 2026
  26. v1.0.9Sep 20, 2026
  27. v1.0.8Sep 17, 2026
  28. v1.0.7Sep 17, 2026
  29. v1.0.6Sep 16, 2026

Score

25% 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 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.