# text-to-reality [Health: Active]

**Category:** 💻 Developer Tools  
**Repository:** https://github.com/ai-wes/text-to-reality  
**GitHub Stars:** 0  
**Views:** 0  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/text-to-reality

## Description
Turn an idea into a device anyone can build: parts, printed parts, wiring, code and a picture guide.

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

```json
"mcpServers": {
  "text-to-reality": {
    "command": "uvx",
    "args": ["text-to-reality"],
    "env": {
      "TEXT_TO_REALITY_DIR": ""
    }
  }
}
```

**Requires environment variables:** `TEXT_TO_REALITY_DIR` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What text-to-reality does

The text-to-reality MCP server helps an AI agent turn a hardware idea into an organized build package. Its output covers more than enclosure geometry: a project can include a requirements brief, orderable parts, 3D-printable case or mounting files, connector-by-connector wiring, firmware source, assembly instructions, and tests with expected passing results.

Projects are stored as ordinary folders on the local machine. The format is intended to support builds that use plug-on connectors instead of loose jumper wires, and the agent can use board header information to select compatible connector arrangements. The repository describes a Seeed Studio XIAO ESP32-S3 and display device as an example workflow.

## How it works

Each project moves through seven areas: requirements, parts, printed parts, electronics, code, assembly, and testing. The requirements file records behavior, dimensions, power, budget, and acceptance criteria. Other files capture the bill of materials, CAD and mesh outputs, wiring data, firmware instructions, picture-based assembly steps, and verification checks.

During the workflow, the local MCP service gives the agent operations for creating projects, adding or recording files, validating the package, maintaining build history, and noticing when checked files have changed. It can also consult board pin layouts and information about plug-on parts. The separate command-line check can inspect an existing project folder.

## Setup and configuration

The package requires Python 3.11 or newer and uses uv. Installation options are provided for Claude Code, Codex, Cursor, and Claude Desktop. Other agents can add the project through the documented skills command and then use the MCP configuration. Claude Desktop runs the server with uvx and a pinned package version in the example configuration.

By default, generated projects are placed in a `text-to-reality/` directory relative to the application’s starting folder. Set `TEXT_TO_REALITY_DIR` in the MCP environment configuration to use a different location. The README states that the server runs locally and does not require an account or API key.

## Tools and capabilities

The text-to-reality MCP server supports these workflow capabilities:

- Create and organize device projects.
- Record requirements, parts, wiring, code, guides, and test data.
- Validate whether a build package is complete and internally checked.
- Track build history.
- Detect edits made after files were checked.
- Look up board header layouts and compatible plug-on parts.
- Check a project folder directly with `uvx text-to-reality check`.

It can work alongside text-to-cad: text-to-reality plans the overall device, while text-to-cad can produce printed parts when that server is available.

## Limitations and notes

The repository describes planning, packaging, validation, and lookup functions; it does not claim to manufacture parts, order components, print objects, flash firmware, or physically test a device. The resulting build still depends on the selected parts, fabrication equipment, and the builder following the guide.

Connector selection centers on JIG_ plug-on connectors by default. The agent records when a connector cannot fit a pin row, but the README does not promise compatibility with every board or component. The example is designed for people without electronics experience and avoids soldering and breadboards, but individual projects may still have hardware constraints that require review.

_Full upstream README: https://allmcps.com/mcp/text-to-reality/readme_