Wyrd logo

Wyrd

Provides read-only MCP access to one user-granted folder, enforcing a documented path-containment boundary.

Install Wyrd

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "wyrd": {
      "command": "npx",
      "args": [
        "-y",
        "wyrd-mcp"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Install not yet sandbox-tested— we haven't run this command through our automated sandbox yet. Not a red flag; we're working through the catalog.

Overview

The wyrd MCP server exposes one folder explicitly granted by the user to an AI client. Access is read-only and constrained by a documented path-containment fence. The repository contains multiple MCP servers and a shared containment library, with package-specific behavior documented separately. Reach for it when an agent needs bounded access to a particular local folder without write access.

Use cases

  • Inspect files in a user-granted workspace
  • Restrict agent access to one directory
  • Review repository contents without allowing writes
  • Build the packages from a clean checkout

Key features

  • Read-only folder access
  • One explicitly granted folder
  • Path-containment boundary
  • Shared containment library
  • Published npm artifacts

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

6/6 checks healthy over the last 41d

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 11d ago via OSV.dev · wyrd-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads911Package downloads in the last 30 days.
Last commit8d agoMost recent push to the default branch.

How Wyrd works

What wyrd MCP server does

The wyrd MCP server is designed around a narrow filesystem boundary: the user grants one folder, and the server operates over that folder. Access is read-only, so the material describes it as suitable for allowing an AI client to inspect a designated workspace without granting the ability to modify files.

The repository is broader than a single server package. Wyrd is described as a collection of MCP servers together with a containment library. Each server uses one explicitly granted folder and follows the path boundary documented by that library. The exact behavior and usage details can differ by package, so the package-local README remains the source for package-specific instructions.

How it works

At a high level, the wyrd MCP server combines MCP access with a user-selected directory and a path-containment rule. Requests are evaluated within the granted folder rather than being treated as unrestricted filesystem access.

The boundary is the central security property documented for the project. The current description also specifies read-only behavior. Together, these constraints make the server appropriate for agents that need to inspect files in a controlled location, but not for workflows requiring edits, file creation, deletion, or access to arbitrary directories.

Setup and configuration

The repository can be built from a clean checkout with:

Terminal
npm install --ignore-scripts --package-lock=false
npm run build

Published npm artifacts are the supported installation path. The repository is provided for inspecting source and configuration and for building the packages. Dependencies resolve within their declared ranges.

Consult the README for the specific package being deployed before configuring an MCP client. Package-local README files document usage, behavior, the security boundary, and the test surface.

Limitations and notes

The wyrd MCP server should not be described as general-purpose filesystem access. Its documented model is one explicitly granted folder with read-only operation and a path-containment fence.

License information is package-specific: each package has its own LICENSE file. The repository scaffold itself is MIT, but that does not establish the license for every published server package. Review the package-local license before redistribution or deployment.

The source repository is not presented as the primary installation mechanism. Use the published npm artifacts for supported installation, and use the repository build commands when inspecting or building from source.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Wyrd

wyrd is an MCP server that connects an AI client to one folder explicitly granted by the user. Its main tools are read-only folder access and path-boundary enforcement: it exposes files within that folder while applying the documented containment fence.

Use the published npm artifacts, which the project identifies as the supported installation path. For a clean-checkout build, run `npm install --ignore-scripts --package-lock=false` followed by `npm run build`; package-specific usage instructions are in each package README.

No, the documented server behavior is read-only.

It describes access for an AI client in general, so client support should be verified against the relevant package documentation.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewWyrd AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/wyrd?style=directory)](https://allmcps.com/mcp/wyrd)
HTML Embed
<a href="https://allmcps.com/mcp/wyrd"><img src="https://allmcps.com/api/badge/wyrd?style=directory" alt="Wyrd on AllMCPs" /></a>