text-to-reality
Turn an idea into a device anyone can build: parts, printed parts, wiring, code and a picture guide.
Install
Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).
text-to-realityclaude mcp add text-to-reality -e 'TEXT_TO_REALITY_DIR=<TEXT_TO_REALITY_DIR>' -- uvx text-to-reality==0.1.1 mcp{
"mcpServers": {
"text-to-reality": {
"command": "uvx",
"args": [
"text-to-reality==0.1.1",
"mcp"
],
"env": {
"TEXT_TO_REALITY_DIR": "<TEXT_TO_REALITY_DIR>"
}
}
}
}Environment variables
TEXT_TO_REALITY_DIRFolder where build projects are saved (default: ./text-to-reality)
Documentation
From the project's README on GitHub, refreshed weekly. Links open on GitHub.
Contents
text-to-reality
Give your agent the power to build real things.
text-to-cad makes a part. text-to-reality makes the working device.
Describe something you want to exist. Your agent turns it into a build package anyone can put together by following pictures:
- a parts list you can order, using parts that plug together
- 3D-printable parts for the case and mounts
- the wiring, every wire and which connector it goes in
- the code, ready to load
- a step-by-step picture guide written for someone who has never built electronics
- tests, so you know it works
No soldering, no breadboard, no electronics experience required. It runs on your machine: no account, no API key, and your projects are plain folders you own.
Example: Agent Meter
"Build me a little desk character that shows what my coding agent is doing and how much of my Claude allowance is left."
Agent Meter illustrates this workflow: a Seeed Studio XIAO ESP32-S3 and a small screen inside a printed character, wired with plug-on connectors, with firmware and a picture guide. Its face shows when your agent is working, finished or waiting on you, plus your remaining allowance.
Install
Ask your agent
Install text-to-reality from https://github.com/ai-wes/text-to-realityOr install it yourself. text-to-reality runs through uv:
check it's installed with uv --version, or use
uv's installer. Then run the
commands for your agent and restart it.
Claude Code
claude plugin marketplace add ai-wes/text-to-reality
claude plugin install text-to-reality@ai-wesTo update: claude plugin marketplace update ai-wes, then
claude plugin update text-to-reality@ai-wes.
Codex
codex plugin marketplace add ai-wes/text-to-reality
codex plugin add text-to-reality@ai-wesCursor
Cursor also loads the Claude Code plugin; if that's installed, skip this.
git clone --depth 1 https://github.com/ai-wes/text-to-reality ~/.cursor/plugins/local/text-to-realityClaude Desktop
Add the server to Claude Desktop's config (Settings > Developer > Edit Config), then
restart. If it can't find uvx, use its full path (which uvx).
{
"mcpServers": {
"text-to-reality": {
"command": "uvx",
"args": ["--no-config", "--managed-python", "--python", "3.13", "--from", "text-to-reality==0.1.1", "text-to-reality", "mcp"]
}
}
}Projects are saved in text-to-reality/ in the folder the app starts in; set
TEXT_TO_REALITY_DIR in env to choose another folder.
Other agents
npx skills add ai-wes/text-to-realityThen add the MCP server above to your agent's MCP config.
Works with text-to-cad
text-to-reality plans the whole device; text-to-cad is great at the printed parts. Install both, and the agent uses text-to-cad for the printed parts when it's available.
How it works
Each build is a folder. The agent fills in seven stages and checks them:
| Stage | What's in it |
|---|---|
| Requirements | brief.md: what it does, size, power, budget, how you'll know it works |
| Parts | bom.json: every part and quantity |
| Printed parts | CAD source and STL/3MF files |
| Electronics | wiring.json: every wire, its color, and its connector |
| Code | firmware source and how to load it |
| Assembly | the picture guide |
| Testing | what to check, and what a pass looks like |
The local MCP server gives the agent tools to create projects, record files, catch files edited after they were checked, validate the package, keep a build history, and look up board header layouts and plug-on parts.
You can also check a folder yourself:
uvx text-to-reality check ./text-to-reality/my-buildParts that plug together
Loose jumper wires fall off and get swapped. JIG_ makes connectors that turn the wires going to one row of pins into a single plug, so wiring becomes plugging things in.
The agent uses JIG_ connectors by default. It looks up each board's pin rows, picks one connector per row, lists what to buy, and notes any row a connector can't fit. Get them at jig-robotics.com →
Each connector is a base that holds the wires in order and a cover that snaps on. The picture guide shows how to load it, close it and plug it on.
License
MIT
Frequently asked questions
What is text-to-reality?
Turn an idea into a device anyone can build: parts, printed parts, wiring, code and a picture guide.
How do I install text-to-reality?
It runs on your machine. In Claude Code: claude mcp add text-to-reality -e 'TEXT_TO_REALITY_DIR=<TEXT_TO_REALITY_DIR>' -- uvx text-to-reality==0.1.1 mcp. For other clients, paste the JSON configuration from this page into their MCP settings.
Does text-to-reality need an API key?
Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.
Is text-to-reality open source?
Yes. Its code is on GitHub under the MIT license.
Who maintains text-to-reality?
It is published by ai-wes. AI.tn lists it but does not maintain or endorse it.
From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.