# wyrd [Health: Active]

**Category:** 📂 File Systems  
**Repository:** https://github.com/MortalPastry/wyrd-mcp  
**GitHub Stars:** 0  
**npm Downloads (last month):** 911  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/wyrd

## Description
Exposes one granted folder to any AI client, read-only, behind a path-containment fence.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "wyrd": {
    "command": "npx",
    "args": ["-y","wyrd-mcp"]
  }
}
```

## Documentation

## 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:

```sh
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.

_Full upstream README: https://allmcps.com/mcp/wyrd/readme_