text-to-reality
Turn an idea into a device anyone can build: parts, printed parts, wiring, code and a picture guide.
Connector by ai-wes · GitHub account verified by the MCP Registry
Chalk Labs
Need help deploying text-to-reality?
Chalk Labs sets up agents like this inside real teams: connected to your tools, tested on your data, with a human in the loop where it matters.
Install
Works with Claude Code, Codex, VS Code, Cursor, Windsurf, Claude Desktop. Read the repository before you give any tool access to your data.
npx agentmarket install connector/ai-wes-text-to-reality
Asks which of your tools to add it to (Claude Code, Codex, Cursor, VS Code, Windsurf, Gemini CLI, Claude Desktop) and shows the change first. See https://agentmart.dev/cli.
Get the weekly diff
The weekly diff: one email a week with new agent tools, notable updates and grade changes, plus security alerts for tools you follow. Double opt-in, one-click unsubscribe.
About
Reviews
Write a reviewNo reviews yet. Installed it? Reviews come from verified installers only. How reviews work
Permissions
What this server can do and what it asks for, from its tool list and install config. Checked Oct 25, 2026.
- Tools
- 5 read · 6 write · 0 delete · 2 not yet classified
- Secrets
- None asked for
- Install scripts
- Not scanned yet
- Runs as
- Python package
Tools by what they do 13
Read from the source code; the running server may list different tools.
Read 5 · Look things up without changing anything.
check_packageconnector_guidancefind_jig_partslist_projectsproject_status
Write 6 · Create, change, send or run things.
build_historycreate_projectlog_outcomenew_revisionrecord_filesset_stage
Not yet classified 2 · We could not tell from the name and description.
board_headersconnectors_for_boards
Secrets and settings it asks for
Other settings (environment variables or headers).
TEXT_TO_REALITY_DIR
Files it touches
- Any path the agent passes to its tools
Tools (13)
Read from the source code; the running server may differ. Descriptions are the server’s own words; hidden characters are shown as [U+…].
board_headersHeader rows (pins per row) for common boards and modules: XIAO, Pico, ESP32 DevKit, Arduino Nano, SSD1306 OLED and more.
build_historyEverything that happened to a build: files recorded, revisions, outcomes.
check_packageCheck the build is complete and consistent: every stage finished, files unchanged since recorded, bom.json and wiring.json valid, JIG_ connectors in the parts list, an assembly guide present. Returns problems to fix and links to get the JIG_ parts the build uses.
connector_guidanceRead this before planning header wiring. Returns what JIG_ connectors are (a base that holds each wire's plug in order plus a snap-on cover), which headers they fit, how many to use, how to list them, and the steps to load them and plug them on.
connectors_for_boardsWhich JIG_ wire connectors a build needs: one per header row, sized to the whole row. `boards` is a list of {"board": name, "quantity": n}, or {"board": label, "rows": [pins, ...], "quantity": n} for a board that isn't in the catalog. `size` is small or large, matching the jumper wire plugs. row_checks lists what to confirm on the real board. Custom `headers` take the catalog row fields plus gender, rows, shrouded and preinstalled.
create_projectStart a build. `brief` is the idea in plain words plus anything known: size, power, budget, parts the person already owns, and how they'll know it works. Creates a folder with brief.md.
find_jig_partsLook up JIG_ parts that remove soldering, crimping and breadboards: wire connectors, a XIAO battery adapter, and complete kits. Empty query lists everything.
list_projectsList builds in the projects folder.
log_outcomeRecord what happened when the build was tried: worked, partly_worked or failed, with what was learned. Read it back with build_history before designing the next one.
new_revisionStart a new revision after a design change. Re-record files you change in it.
project_statusShow each stage, its files, what to do next, and files edited since they were recorded.
record_filesRecord files you've written (paths relative to the project folder) under a stage: requirements, parts, mechanical, electronics, firmware, assembly or testing. Recording fingerprints each file so later edits are caught.
set_stageSet a stage to todo, done or not_applicable. not_applicable needs a reason (for example, a printed-only object has no electronics).
Signals
- Stars
- 1
- Forks
- 0
- Open issues
- 0
- Weekly downloads
- 22
- Last commit
- Oct 7, 2026 (24 days ago)
- Last release
- Oct 7, 2026 (24 days ago)
- Last package publish
- Oct 7, 2026 (24 days ago)
From GitHub (fetched Oct 24, 2026) and the package registry.
Details
- Registry name
io.github.ai-wes/text-to-reality- Version
- 0.1.1
- Auth
- No auth
- Packages
- pypi text-to-reality
- License
- MIT
- Repository
- github.com/ai-wes/text-to-reality
- First seen
- Oct 24, 2026
- Last checked
- Oct 25, 2026
Done for you
Rather not set it up yourself?
Chalk Labs scopes, builds and runs agents for your team: the task audit, the eval harness, the integrations and the weekly ops report. Fixed scope, priced before we start.
See how we build AI agents →Read the case studies
Chalk Labs is a two-founder AI and growth studio. We build AI agents, CRMs and MVPs for Web3 and AI companies, and have shipped 50+ product and token launches.
- launches shipped
- 50+
- launches shipped
- media placements
- 500+
- media placements
- founders on every account
- 2
- founders on every account
Press we've placed: Forbes · CoinDesk · Decrypt · Cointelegraph · The Block
Rahil Jain, Co-founder, Chalk Labs. Ex-Goldman Sachs engineer. You talk to the person who builds it.
Get text-to-reality running in your business
Tell us what you want to automate. A founder replies within one working day with a plan, not a pitch deck.
Cite this page
text-to-reality MCP server. Agent Mart. https://agentmart.dev/connectors/ai-wes-text-to-reality (last updated 2026-10-25)