
Wyrd
com.wyrdmcpPublished by wyrdmcp.comv0.4.0Updated Oct 24, 2026
Exposes one granted folder to any AI client, read-only, behind a path-containment fence.
Overview
Wyrd exposes one user-granted folder to an AI client as read-only file access, confined behind a path-containment fence.
- What you can do
- Wyrd is a local MCP server that serves exactly one folder that the user explicitly grants. It exposes that folder to any AI client in read-only mode, so the assistant can read files within the granted directory. Access is enforced by a documented path boundary that keeps requests inside the granted folder. The manifest does not list individual tool names.
- When to use it
- Use it when you want an AI assistant to read files from a specific local folder without giving it write access or access to the rest of your machine. It fits workflows where a single project or document directory should be exposed to the client.
- Requirements
- Runs as a local process over stdio, installed from the npm package wyrd-mcp (for example via npx). It requires an absolute path to the folder to serve, set either with the --grant argument or the WYRD_GRANT environment variable; the server refuses to start if neither is set. No authentication is declared.
Installation
In SourceWeft
- Open Wyrd in the dashboard and add it to a workspace.
- 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.
Other MCP clients
Follow the launch instructions in the repository.
README
Wyrd
Wyrd is a collection of MCP servers and their containment library. Each server operates over one folder explicitly granted by the user and applies the library's documented path boundary.
Install the Reader
The published npm package is wyrd-mcp. For Claude Code, run:
See the Reader README for other clients, the security boundary, and known limits. AI agents should follow llms-install.md.
Build from source
Build the workspaces from a clean checkout with:
Each package's README documents that package's usage, behavior, security boundary, and test
surface. Its package-local LICENSE defines its license. The repository scaffold itself is MIT.
Published npm artifacts remain the supported installation path; this repository exposes source and
configuration for inspection and building, with dependencies resolving inside their declared
ranges.
Source: README.md at commit f74b722
Tools
0Version history
6- v0.4.0LatestOct 20, 2026
- v0.3.2Oct 16, 2026
- v0.3.1Oct 16, 2026
- v0.3.0Oct 6, 2026
- v0.2.0Sep 23, 2026
- v0.1.4Sep 16, 2026
Score
50% 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
- License10 pts